View XRT86VL34IB_627811.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

XRT86VL3x
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
JULY 2006 REV. 1.2.0
GENERAL DESCRIPTION
The XRT86VL3x is a 1.544 Mbit/s or 2.048 Mbit/s DS1/E1/J1 framer and LIU integrated solution featuring R3 technology (Relayless, Reconfigurable, Redundancy) that comes in a 2-channel, 4-channel, or 8-channel package. The physical interface is optimized with internal impedance, and with the patented pad structure, the XRT86VL3x provides protection from power failures and hot swapping. The XRT86VL3x contains an integrated DS1/E1/J1 framer and LIU which provide DS1/E1/J1 framing and error accumulation in accordance with ANSI/ITU_T specifications. Each framer has its own framing synchronizer and transmit-receive slip buffers. The slip buffers can be independently enabled or disabled as required and can be configured to frame to the common DS1/E1/J1 signal formats. Each Framer block contains its own Transmit and Receive T1/E1/J1 Framing function. There are 3 Transmit HDLC controllers per channel which encapsulate contents of the Transmit HDLC buffers into LAPD Message frames. There are 3 Receive HDLC controllers per channel which extract the
payload content of Receive LAPD Message frames from the incoming T1/E1/J1 data stream and write the contents into the Receive HDLC buffers. Each framer also contains a Transmit and Overhead Data Input port, which permits Data Link Terminal Equipment direct access to the outbound T1/E1/J1 frames. Likewise, a Receive Overhead output data port permits Data Link Terminal Equipment direct access to the Data Link bits of the inbound T1/E1/J1 frames. The XRT86VL3x fully meets all of the latest T1/E1/J1 specifications: ANSI T1/E1.107-1988, ANSI T1/ E1.403-1995, ANSI T1/E1.231-1993, ANSI T1/ E1.408-1990, AT&T TR 62411 (12-90) TR54016, and ITU G-703, G.704, G706 and G.733, AT&T Pub. 43801, and ETS 300 011, 300 233, JT G.703, JT G.704, JT G706, I.431. Extensive test and diagnostic functions include Loop-backs, Boundary scan, Pseudo Random bit sequence (PRBS) test pattern generation, Performance Monitor, Bit Error Rate (BER) meter, forced error insertion, and LAPD unchannelized data payload processing according to ITU-T standard Q.921. Applications and Features (next page)
FIGURE 1. XRT86VL3X N-CHANNEL DS1 (T1/E1/J1) FRAMER/LIU COMBO
External Data Link Controller
Local PCM Highway
XRT86VL3x
1 of N-channels Tx Serial Data In
Tx Overhead In
Rx Overhead Out
1:2 Turns Ratio TTIP
2-Frame Slip Buffer Elastic Store
Tx Framer
Tx LIU Interface LLB LB
TRING
Tx Serial Clock
ST-BUS
Rx Serial Data Out
Rx Serial Clock
2-Frame Slip Buffer Elastic Store
RTIP
1:1 Turns Ratio
Rx Framer
Rx LIU Interface
RRING
PRBS Generator & Analyser
Performance Monitor
HDLC/LAPD Controllers
LIU & Loopback Control
RxLOS
8kHz sync OSC Signaling & Alarms JTAG DMA Interface
Line Side
Microprocessor Interface
Back Plane 1.544-16.384 Mbit/s
3
4
System (Terminal) Side
TxON Memory
INT
D[7:0]
A[14:0]
P Select
WR ALE_AS RD RDY_DTACK
Intel/Motorola P Configuration, Control & Status Monitor
Exar Corporation 48720 Kato Road, Fremont CA, 94538 * (510) 668-7000 * FAX (510) 668-7017 * www.exar.com
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION APPLICATIONS
REV. 1.2.0
* 3 Integrated HDLC controllers per channel for
transmit and receive, each controller having two 96-byte buffers (buffer 0 / buffer 1)
* High-Density T1/E1/J1 interfaces for Multiplexers,
Switches, LAN Routers and Digital Modems
* SONET/SDH terminal or Add/Drop multiplexers
(ADMs)
* T1/E1/J1 add/drop multiplexers (MUX) * Channel Service Units (CSUs): T1/E1/J1 and
Fractional T1/E1/J1
* HDLC Controllers Support SS7 * Timeslot assignable HDLC * V5.1 or V5.2 Interface * Automatic Performance Report Generation (PMON
Status) can be inserted into the transmit LAPD interface every 1 second or for a single transmission
* Digital Access Cross-connect System (DACs) * Digital Cross-connect Systems (DCS) * Frame Relay Switches and Access Devices
(FRADS)
* Alarm Indication Signal with Customer Installation
signature (AIS-CI)
* ISDN Primary Rate Interfaces (PRA) * PBXs and PCM channel bank * T3 channelized access concentrators and M13
MUX
* Remote Alarm Indication with Customer Installation
(RAI-CI)
* Gapped Clock interface mode for Transmit and
Receive.
* Intel/Motorola and Power PC interfaces for
configuration, control and status monitoring
* Wireless base stations * ATM equipment with integrated DS1 interfaces * Multichannel DS1 Test Equipment * T1/E1/J1 Performance Monitoring * Voice over packet gateways * Routers
FEATURES
* Parallel
search synchronization
algorithm
for
fast
frame
* Wide choice of T1 framing structures: SF/D4, ESF,
SLC(R)96, T1DM and N-Frame (non-signaling)
* Direct access to D and E channels for fast
transmission of data link information
* PRBS, QRSS, and Network Loop Code generation
and detection
* Independent, full duplex DS1 Tx and Rx Framer/
LIUs
* Two 512-bit (two-frame) elastic store, PCM frame
slip buffers (FIFO) on TX and Rx provide up to 8.192 MHz asynchronous back plane connections with jitter and wander attenuation
* Programmable Interrupt output pin * Supports programmed I/O and DMA modes of
Read-Write access
* Each framer block encodes and decodes the T1/
E1/J1 Frame serial data
* Supports input PCM and signaling data at 1.544,
2.048, 4.096 and 8.192 Mbits. Also supports 4channel multiplexed 12.352/16.384 (HMVIP/H.100) Mbit/s on the back plane bus
* Detects and forces Red (SAI), Yellow (RAI) and
Blue (AIS) Alarms
* Detects OOF, LOF, LOS errors and COFA
conditions
* Programmable output clocks for Fractional T1/E1/
J1
* Supports Channel Associated Signaling (CAS) * Supports Common Channel Signalling (CCS) * Supports ISDN Primary Rate Interface (ISDN PRI)
signaling
* Loopbacks: Local (LLB) and Line remote (LB) * Facilitates Inverse Multiplexing for ATM * Performance monitor with one second polling * Boundary scan (IEEE 1149.1) JTAG test port * Accepts external 8kHz Sync reference * 1.8V Inner Core Voltage * 3.3V I/O operation with 5V tolerant inputs
* Extracts and inserts robbed bit signaling (RBS)
2
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
ORDERING INFORMATION
PART NUMBER XRT86VL38IB XRT86VL38IB484 XRT86VL34IB XRT86VL32IB PACKAGE 420 Tape Ball Grid Array 484 Shrink Thin Ball Grid Array 225 Plastic Ball Grid Array 225 Plastic Ball Grid Array OPERATING TEMPERATURE RANGE -40C to +85C -40C to +85C -40C to +85C -40C to +85C
3
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
LIST OF PARAGRAPHS
1.0 GENERAL DESCRIPTION AND INTERFACE .........................................................................................4
1.1 PHYSICAL INTERFACE ...................................................................................................................................... 4 1.2 R3 TECHNOLOGY (RELAYLESS / RECONFIGURABLE / REDUNDANCY) .................................................... 5
1.2.1 LINE CARD REDUNDANCY ........................................................................................................................................... 5 1.2.2 TYPICAL REDUNDANCY SCHEMES ............................................................................................................................ 5 1.2.3 1:1 AND 1+1 REDUNDANCY WITHOUT RELAYS ........................................................................................................ 5 1.2.4 TRANSMIT INTERFACE WITH 1:1 AND 1+1 REDUNDANCY ...................................................................................... 5 1.2.5 RECEIVE INTERFACE WITH 1:1 AND 1+1 REDUNDANCY ......................................................................................... 6
1.3 POWER FAILURE PROTECTION ....................................................................................................................... 7 1.4 OVERVOLTAGE AND OVERCURRENT PROTECTION .................................................................................... 7 1.5 NON-INTRUSIVE MONITORING ......................................................................................................................... 7 1.6 T1/E1 SERIAL PCM INTERFACE ....................................................................................................................... 8 1.7 T1/E1 FRACTIONAL INTERFACE ...................................................................................................................... 9 1.8 T1/E1 TIME SLOT SUBSTITUTION AND CONTROL ....................................................................................... 10 1.9 ROBBED BIT SIGNALING/CAS SIGNALING ................................................................................................... 11 1.10 OVERHEAD INTERFACE ................................................................................................................................ 12 1.11 FRAMER BYPASS MODE ............................................................................................................................... 14 1.12 HIGH-SPEED NON-MULTIPLEXED INTERFACE .......................................................................................... 15 1.13 HIGH-SPEED MULTIPLEXED INTERFACE ................................................................................................... 16
2.0 LOOPBACK MODES OF OPERATION .................................................................................................17
2.1 LIU PHYSICAL INTERFACE LOOPBACK DIAGNOSTICS .............................................................................. 17
2.1.1 LOCAL ANALOG LOOPBACK .................................................................................................................................... 17 2.1.2 REMOTE LOOPBACK .................................................................................................................................................. 17 2.1.3 DIGITAL LOOPBACK ................................................................................................................................................... 18 2.1.4 DUAL LOOPBACK ....................................................................................................................................................... 18 2.1.5 FRAMER REMOTE LINE LOOPBACK ........................................................................................................................ 19 2.1.6 FRAMER LOCAL LOOPBACK ..................................................................................................................................... 19
2.2 PROGRAMMING SEQUENCE FOR SENDING LESS THAN 96-BYTE MESSAGES ...................................... 20 2.3 PROGRAMMING SEQUENCE FOR SENDING LARGE MESSAGES ............................................................. 20 2.4 PROGRAMMING SEQUENCE FOR RECEIVING LAPD MESSAGES ............................................................. 21 2.5 SS7 (SIGNALING SYSTEM NUMBER 7) FOR ESF IN DS1 ONLY .................................................................. 21 2.6 DS1/E1 DATALINK TRANSMISSION USING THE HDLC CONTROLLERS ................................................... 21 2.7 TRANSMIT BOS (BIT ORIENTED SIGNALING) PROCESSOR ....................................................................... 21
2.7.1 DESCRIPTION OF BOS ................................................................................................................................................ 21 2.7.2 PRIORITY CODEWORD MESSAGE ............................................................................................................................ 22 2.7.3 COMMAND AND RESPONSE INFORMATION ............................................................................................................ 22
2.8 TRANSMIT MOS (MESSAGE ORIENTED SIGNALING) PROCESSOR .......................................................... 22
2.8.1 DISCUSSION OF MOS ................................................................................................................................................. 22 2.8.2 PERIODIC PERFORMANCE REPORT ........................................................................................................................ 23 2.8.3 TRANSMISSION-ERROR EVENT ................................................................................................................................ 23 2.8.4 PATH AND TEST SIGNAL IDENTIFICATION MESSAGE ........................................................................................... 24 2.8.5 FRAME STRUCTURE ................................................................................................................................................... 24 2.8.6 FLAG SEQUENCE ........................................................................................................................................................ 24 2.8.7 ADDRESS FIELD .......................................................................................................................................................... 24 2.8.8 ADDRESS FIELD EXTENSION BIT (EA) ..................................................................................................................... 24 2.8.9 COMMAND OR RESPONSE BIT (C/R) ........................................................................................................................ 24 2.8.10 SERVICE ACCESS POINT IDENTIFIER (SAPI) ........................................................................................................ 25 2.8.11 TERMINAL ENDPOINT IDENTIFIER (TEI) ................................................................................................................. 25 2.8.12 CONTROL FIELD ........................................................................................................................................................ 25 2.8.13 FRAME CHECK SEQUENCE (FCS) FIELD ............................................................................................................... 25 2.8.14 TRANSPARENCY (ZERO STUFFING) ....................................................................................................................... 25
2.9 TRANSMIT SLC(R)96 DATA LINK CONTROLLER ............................................................................................ 26 2.10 D/E TIME SLOT TRANSMIT HDLC CONTROLLER BLOCK V5.1 OR V5.2 INTERFACE ............................ 27 2.11 AUTOMATIC PERFORMANCE REPORT (APR) ............................................................................................ 27
2.11.1 BIT VALUE INTERPRETATION ................................................................................................................................. 27
3.0 OVERHEAD INTERFACE BLOCK ........................................................................................................29
3.1 DS1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK ............................................................................. 29
3.1.1 DESCRIPTION OF THE DS1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK ................................................ 29 3.1.2 CONFIGURE THE DS1 TRANSMIT OVERHEAD INPUT INTERFACE MODULE AS SOURCE OF THE FACILITY DATA LINK (FDL) BITS IN ESF FRAMING FORMAT MODE ................................................................................................. 29 3.1.3 CONFIGURE THE DS1 TRANSMIT OVERHEAD INPUT INTERFACE MODULE AS SOURCE OF THE SIGNALING
I
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FRAMING (FS) BITS IN N OR SLC(R)96 FRAMING FORMAT MODE .......................................................................... 31 3.1.4 CONFIGURE THE DS1 TRANSMIT OVERHEAD INPUT INTERFACE MODULE AS SOURCE OF THE REMOTE SIGNALING (R) BITS IN T1DM FRAMING FORMAT MODE ............................................................................................. 32
3.2 DS1 RECEIVE OVERHEAD OUTPUT INTERFACE BLOCK ........................................................................... 33
3.2.1 DESCRIPTION OF THE DS1 RECEIVE OVERHEAD OUTPUT INTERFACE BLOCK ............................................... 33 3.2.2 CONFIGURE THE DS1 RECEIVE OVERHEAD OUTPUT INTERFACE MODULE AS DESTINATION OF THE FACILITY DATA LINK (FDL) BITS IN ESF FRAMING FORMAT MODE ...................................................................................... 33 3.2.3 CONFIGURE THE DS1 RECEIVE OVERHEAD OUTPUT INTERFACE MODULE AS DESTINATION OF THE SIGNALING FRAMING (FS) BITS IN N OR SLC(R)96 FRAMING FORMAT MODE .......................................................................... 35 3.2.4 CONFIGURE THE DS1 RECEIVE OVERHEAD OUTPUT INTERFACE MODULE AS DESTINATION OF THE REMOTE SIGNALING (R) BITS IN T1DM FRAMING FORMAT MODE ....................................................................................... 36
3.3 E1 OVERHEAD INTERFACE BLOCK .............................................................................................................. 37 3.4 E1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK ............................................................................... 37
3.4.1 DESCRIPTION OF THE E1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK ................................................... 37 3.4.2 CONFIGURE THE E1 TRANSMIT OVERHEAD INPUT INTERFACE MODULE AS SOURCE OF THE NATIONAL BIT SEQUENCE IN E1 FRAMING FORMAT MODE ................................................................................................................ 38
3.5 E1 RECEIVE OVERHEAD INTERFACE ........................................................................................................... 41
3.5.1 DESCRIPTION OF THE E1 RECEIVE OVERHEAD OUTPUT INTERFACE BLOCK ................................................. 41 3.5.2 CONFIGURE THE E1 RECEIVE OVERHEAD OUTPUT INTERFACE MODULE AS SOURCE OF THE NATIONAL BIT SEQUENCE IN E1 FRAMING FORMAT MODE ............................................................................................................ 41
4.0 LIU TRANSMIT PATH ........................................................................................................................... 43
4.1 TRANSMIT DIAGNOSTIC FEATURES ............................................................................................................. 43
4.1.1 TAOS (TRANSMIT ALL ONES) .................................................................................................................................... 43 4.1.2 ATAOS (AUTOMATIC TRANSMIT ALL ONES) ........................................................................................................... 43 4.1.3 NETWORK LOOP UP CODE ........................................................................................................................................ 43 4.1.4 NETWORK LOOP DOWN CODE ................................................................................................................................. 44 4.1.5 QRSS GENERATION .................................................................................................................................................... 44
4.2 T1 LONG HAUL LINE BUILD OUT (LBO) ........................................................................................................ 44 4.3 T1 SHORT HAUL LINE BUILD OUT (LBO) ...................................................................................................... 47
4.3.1 ARBITRARY PULSE GENERATOR ............................................................................................................................. 47 4.3.2 DMO (DIGITAL MONITOR OUTPUT) ........................................................................................................................... 48 4.3.3 TRANSMIT JITTER ATTENUATOR ............................................................................................................................. 48
4.4 LINE TERMINATION (TTIP/TRING) .................................................................................................................. 48
5.0 LIU RECEIVE PATH .............................................................................................................................. 49
5.1 LINE TERMINATION (RTIP/RRING) ................................................................................................................. 49
5.1.1 INTERNAL TERMINATION ........................................................................................................................................... 49 5.1.2 EQUALIZER CONTROL ............................................................................................................................................... 49 5.1.3 CABLE LOSS INDICATOR ........................................................................................................................................... 50
5.2 RECEIVE SENSITIVITY ..................................................................................................................................... 50
5.2.1 AIS (ALARM INDICATION SIGNAL) ............................................................................................................................ 51 5.2.2 NLCD (NETWORK LOOP CODE DETECTION) ........................................................................................................... 51 5.2.3 FLSD (FIFO LIMIT STATUS DETECTION) .................................................................................................................. 52 5.2.4 RECEIVE JITTER ATTENUATOR ................................................................................................................................ 52 5.2.5 RXMUTE (RECEIVER LOS WITH DATA MUTING) ..................................................................................................... 52
6.0 THE E1 TRANSMIT/RECEIVE FRAMER .............................................................................................. 54
6.1 DESCRIPTION OF THE TRANSMIT/RECEIVE PAYLOAD DATA INPUT INTERFACE BLOCK .................... 54
6.1.1 BRIEF DISCUSSION OF THE TRANSMIT/RECEIVE PAYLOAD DATA INPUT INTERFACE BLOCK OPERATING AT XRT84V24 COMPATIBLE 2.048MBIT/S MODE ........................................................................................................... 54
6.2 TRANSMIT/RECEIVE HIGH-SPEED BACK-PLANE INTERFACE .................................................................. 56
6.2.1 NON-MULTIPLEXED HIGH-SPEED MODE ................................................................................................................. 56 6.2.2 MULTIPLEXED HIGH-SPEED MODE .......................................................................................................................... 59
6.3 BRIEF DISCUSSION OF COMMON CHANNEL SIGNALING IN E1 FRAMING FORMAT .............................. 65 6.4 BRIEF DISCUSSION OF CHANNEL ASSOCIATED SIGNALING IN E1 FRAMING FORMAT ....................... 65 6.5 INSERT/EXTRACT SIGNALING BITS FROM TSCR REGISTER .................................................................... 65 6.6 INSERT/EXTRACT SIGNALING BITS FROM TXCHN[0]_N/TXSIG PIN ......................................................... 65 6.7 ENABLE CHANNEL ASSOCIATED SIGNALING AND SIGNALING DATA SOURCE CONTROL ................. 66
7.0 THE DS1 TRANSMIT/RECEIVE FRAMER ............................................................................................ 67
7.1 DESCRIPTION OF THE TRANSMIT/RECEIVE PAYLOAD DATA INPUT INTERFACE BLOCK .................... 67
7.1.1 BRIEF DISCUSSION OF THE TRANSMIT/RECEIVE PAYLOAD DATA INPUT INTERFACE BLOCK OPERATING AT 1.544MBIT/S MODE ....................................................................................................................................................... 67
7.2 TRANSMIT/RECEIVE HIGH-SPEED BACK-PLANE INTERFACE .................................................................. 69
7.2.1 T1 TRANSMIT/RECEIVE INTERFACE - MVIP 2.048 MHZ .......................................................................................... 69 7.2.2 NON-MULTIPLEXED HIGH-SPEED MODE ................................................................................................................. 70 7.2.3 MULTIPLEXED HIGH-SPEED MODE .......................................................................................................................... 72
II
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
7.3 BRIEF DISCUSSION OF ROBBED-BIT SIGNALING IN DS1 FRAMING FORMAT ........................................ 81
7.3.1 CONFIGURE THE FRAMER TO TRANSMIT ROBBED-BIT SIGNALING ................................................................... 82 7.3.2 INSERT SIGNALING BITS FROM TSCR REGISTER .................................................................................................. 82 7.3.3 INSERT SIGNALING BITS FROM TXSIG_N PIN ......................................................................................................... 83
8.0 ALARMS AND ERROR CONDITIONS ..................................................................................................85
8.1 AIS ALARM ........................................................................................................................................................ 85 8.2 RED ALARM ...................................................................................................................................................... 87 8.3 YELLOW ALARM .............................................................................................................................................. 88 8.4 BIPOLAR VIOLATION ....................................................................................................................................... 90 8.5 E1 BRIEF DISCUSSION OF ALARMS AND ERROR CONDITIONS ............................................................... 92
8.5.1 HOW TO CONFIGURE THE FRAMER TO TRANSMIT AIS ........................................................................................ 98 8.5.2 HOW TO CONFIGURE THE FRAMER TO GENERATE RED ALARM ....................................................................... 99 8.5.3 HOW TO CONFIGURE THE FRAMER TO TRANSMIT YELLOW ALARM ................................................................. 99 8.5.4 TRANSMIT YELLOW ALARM .................................................................................................................................... 100 8.5.5 TRANSMIT CAS MULTI-FRAME YELLOW ALARM ................................................................................................. 100
8.6 T1 BRIEF DISCUSSION OF ALARMS AND ERROR CONDITIONS .............................................................. 101
8.6.1 HOW TO CONFIGURE THE FRAMER TO TRANSMIT AIS ...................................................................................... 104 8.6.2 HOW TO CONFIGURE THE FRAMER TO GENERATE RED ALARM ..................................................................... 105 8.6.3 HOW TO CONFIGURE THE FRAMER TO TRANSMIT YELLOW ALARM ............................................................... 105 8.6.4 TRANSMIT YELLOW ALARM IN SF MODE .............................................................................................................. 106 8.6.5 TRANSMIT YELLOW ALARM IN ESF MODE ............................................................................................................ 106 8.6.6 TRANSMIT YELLOW ALARM IN N MODE ................................................................................................................ 106 8.6.7 TRANSMIT YELLOW ALARM IN T1DM MODE ......................................................................................................... 106
9.0 APPENDIX A: DS-1/E1 FRAMING FORMATS ....................................................................................108
9.1 THE E1 FRAMING STRUCTURE .................................................................................................................... 108
9.1.1 FAS FRAME ................................................................................................................................................................ 108 9.1.2 NON-FAS FRAME ....................................................................................................................................................... 109
9.2 THE E1 MULTI-FRAME STRUCTURE ............................................................................................................ 110
9.2.1 THE CRC MULTI-FRAME STRUCTURE .................................................................................................................... 110 9.2.2 CAS MULTI-FRAMES AND CHANNEL ASSOCIATED SIGNALING ........................................................................ 111
9.3 THE DS1 FRAMING STRUCTURE .................................................................................................................. 113 9.4 T1 SUPER FRAME FORMAT (SF) .................................................................................................................. 114 9.5 T1 EXTENDED SUPERFRAME FORMAT (ESF) ............................................................................................ 115 9.6 T1 NON-SIGNALING FRAME FORMAT ......................................................................................................... 117 9.7 T1 DATA MULTIPLEXED FRAMING FORMAT (T1DM) ................................................................................. 117 9.8 SLC-96 FORMAT (SLC-96) ............................................................................................................................. 118
III
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
LIST OF FIGURES
Figure 1.: XRT86VL3x N-Channel DS1 (T1/E1/J1) Framer/LIU Combo ........................................................................... 1 Figure 2.: LIU Transmit Connection Diagram Using Internal Termination ......................................................................... 4 Figure 3.: LIU Receive Connection Diagram Using Internal Termination ......................................................................... 4 Figure 4.: Simplified Block Diagram of the Transmit Interface for 1:1 and 1+1 Redundancy ............................................ 5 Figure 5.: Simplified Block Diagram of the Receive Interface for 1:1 and 1+1 Redundancy ............................................. 6 Figure 6.: Simplified Block Diagram of a Non-Intrusive Monitoring Application ................................................................. 7 Figure 7.: Transmit T1/E1 Serial PCM Interface ................................................................................................................ 8 Figure 8.: Receive T1/E1 Serial PCM Interface ................................................................................................................. 8 Figure 9.: T1 Fractional Interface ....................................................................................................................................... 9 Figure 10.: T1/E1 Time Slot Substitution and Control ..................................................................................................... 10 Figure 11.: Robbed Bit Signaling / CAS Signaling ........................................................................................................... 11 Figure 12.: ESF / CAS External Signaling Bus ................................................................................................................ 11 Figure 13.: SF / SLC-96 or 4-code Signaling in ESF / CAS External Signaling Bus ....................................................... 12 Figure 14.: T1/E1 Overhead Interface ............................................................................................................................. 12 Figure 15.: T1 External Overhead Datalink Bus .............................................................................................................. 13 Figure 16.: E1 Overhead External Datalink Bus .............................................................................................................. 13 Figure 17.: Simplified Block Diagram of the Framer Bypass Mode ................................................................................. 14 Figure 18.: T1 High-Speed Non-Multiplexed Interface .................................................................................................... 15 Figure 19.: E1 High-Speed Non-Multiplexed Interface .................................................................................................... 15 Figure 20.: Transmit High-Speed Bit Multiplexed Block Diagram .................................................................................... 16 Figure 21.: Receive High-Speed Bit Multiplexed Block Diagram ..................................................................................... 16 Figure 22.: Simplified Block Diagram of Local Analog Loopback .................................................................................... 17 Figure 23.: Simplified Block Diagram of Remote Loopback ............................................................................................ 17 Figure 24.: Simplified Block Diagram of Digital Loopback ............................................................................................... 18 Figure 25.: Simplified Block Diagram of Dual Loopback .................................................................................................. 18 Figure 26.: Simplified Block Diagram of the Framer Remote Line Loopback .................................................................. 19 Figure 27.: Simplified Block Diagram of the Framer Local Loopback .............................................................................. 19 Figure 28.: HDLC Controllers .......................................................................................................................................... 20 Figure 29.: LAPD Frame Structure .................................................................................................................................. 23 Figure 30.: Block Diagram of the DS1 Transmit Overhead Input Interface of the XRT86VL3x ....................................... 29 Figure 31.: DS1 Transmit Overhead Input Interface Timing in ESF Framing Format mode ............................................ 31 Figure 32.: DS1 Transmit Overhead Input Timing in N or SLC(R)96 Framing Format Mode ............................................ 32 Figure 33.: DS1 Transmit Overhead Input Interface module in T1DM Framing Format mode ........................................ 32 Figure 34.: Block Diagram of the DS1 Receive Overhead Output Interface of XRT86VL3x ........................................... 33 Figure 35.: DS1 Receive Overhead Output Interface module in ESF framing format mode ........................................... 35 Figure 36.: DS1 Receive Overhead Output Interface Timing in N or SLC(R)96 Framing Format mode ........................... 36 Figure 37.: DS1 Receive Overhead Output Interface Timing in T1DM Framing Format mode ....................................... 37 Figure 38.: Block Diagram of the E1 Transmit Overhead Input Interface of XRT86VL3x ................................................ 38 Figure 39.: E1 Transmit Overhead Input Interface Timing ............................................................................................... 40 Figure 40.: Block Diagram of the E1 Receive Overhead Output Interface of XRT86VL3x .............................................. 41 Figure 41.: E1 Receive Overhead Output Interface Timing ............................................................................................. 42 Figure 42.: TAOS (Transmit All Ones) ............................................................................................................................. 43 Figure 43.: Simplified Block Diagram of the ATAOS Function ......................................................................................... 43 Figure 44.: Network Loop Up Code Generation .............................................................................................................. 44 Figure 45.: Network Loop Down Code Generation .......................................................................................................... 44 Figure 46.: Long Haul Line Build Out with -7.5dB Attenuation ........................................................................................ 45 Figure 47.: Long Haul Line Build Out with -15dB Attenuation ......................................................................................... 45 Figure 48.: Long Haul Line Build Out with -22.5dB Attenuation ...................................................................................... 46 Figure 49.: Arbitrary Pulse Segment Assignment ............................................................................................................ 47 Figure 50.: Typical Connection Diagram Using Internal Termination .............................................................................. 48 Figure 51.: Typical Connection Diagram Using Internal Termination ............................................................................. 49 Figure 52.: Simplified Block Diagram of the Equalizer and Peak Detector ...................................................................... 50 Figure 53.: Simplified Block Diagram of the Cable Loss Indicator ................................................................................... 50 Figure 54.: Test Configuration for Measuring Receive Sensitivity ................................................................................... 51 Figure 55.: Process Block for Automatic Loop Code Detection ....................................................................................... 52 Figure 56.: Simplified Block Diagram of the RxMUTE Function ...................................................................................... 53 Figure 57.: Interfacing the Transmit Path to local terminal equipment ............................................................................ 54 Figure 59.: Waveforms for connecting the Transmit Payload Data Input Interface Block to local Terminal Equipment .. 55
IV
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
Figure 58.: Interfacing the Receive Path to local terminal equipment .............................................................................. 55 Figure 60.: Waveforms for connecting the Receive Payload Data Input Interface Block to local Terminal Equipment ... 56 Figure 61.: Transmit Non-Multiplexed High-Speed Connection to local terminal equipment using MVIP 2.048Mbit/s, 4.096Mbit/s, or 8.192Mbit/s ............................................................................................................................... 57 Figure 62.: Receive Non-Multiplexed High-Speed Connection to local terminal equipment using MVIP 2.048Mbit/s, 4.096Mbit/s, or 8.192Mbit/s ............................................................................................................................... 57 Figure 63.: Waveforms for Connecting the Transmit Non-Multiplexed High-Speed Input Interface at MVIP 2.048Mbit/s, 4.096Mbit/s, and 8.192Mbit/s ............................................................................................................................ 58 Figure 64.: Waveforms for Connecting the Receive Non-Multiplexed High-Speed Input Interface at MVIP 2.048Mbit/s, 4.096Mbit/s, and 8.192Mbit/s ............................................................................................................................ 58 Figure 65.: Interfacing XRT86VL3x Transmit to local terminal equipment using 16.384Mbit/s, HMVIP 16.384Mbit/s, and H.100 16.384Mbit/s ........................................................................................................................................... 62 Figure 66.: Timing signal when the framer is running at Bit-Multiplexed 16.384Mbit/s mode .......................................... 62 Figure 67.: Waveforms for Connecting the Transmit Multiplexed High-Speed Input Interface at HMVIP And H.100 16.384Mbit/s mode ............................................................................................................................................ 63 Figure 68.: Interfacing XRT86VL3x Receive to local terminal equipment using 16.384Mbit/s, HMVIP 16.384Mbit/s, and H.100 16.384Mbit/s ........................................................................................................................................... 64 Figure 69.: Timing Signal When the Receive Framer is running at 16.384MHz Bit-Mulitplexed Mode ........................... 64 Figure 70.: Timing Signal wehn the Receive Framer is Running at HMVIP and H100 16.384MHz Mode ...................... 64 Figure 71.: Timing Diagram of the TxSIG Input ............................................................................................................... 66 Figure 72.: Timing Diagram of the RxSIG Output ............................................................................................................ 66 Figure 73.: Interfacing the Transmit Path to local terminal equipment ............................................................................. 67 Figure 75.: Waveforms for connecting the Transmit Payload Data Input Interface Block to local Terminal Equipment .. 68 Figure 74.: Interfacing the Receive Path to local terminal equipment .............................................................................. 68 Figure 76.: Waveforms for connecting the Receive Payload Data Input Interface Block to local Terminal Equipment ... 69 Figure 77.: Transmit Non-Multiplexed High-Speed Connection to local terminal equipment using MVIP 2.048Mbit/s, 4.096Mbit/s, or 8.192Mbit/s ............................................................................................................................... 70 Figure 79.: Waveforms for Connecting the Transmit Non-Multiplexed High-Speed Input Interface at MVIP 2.048Mbit/s, 4.096Mbit/s, and 8.192Mbit/s ............................................................................................................................ 71 Figure 78.: Receive Non-Multiplexed High-Speed Connection to local terminal equipment using MVIP 2.048Mbit/s, 4.096Mbit/s, or 8.192Mbit/s ............................................................................................................................... 71 Figure 80.: Waveforms for Connecting the Receive Non-Multiplexed High-Speed Input Interface at MVIP 2.048Mbit/s, 4.096Mbit/s, and 8.192Mbit/s ............................................................................................................................ 72 Figure 81.: Interfacing XRT86VL3x Transmit to local terminal equipment using 16.384Mbit/s, HMVIP 16.384Mbit/s, and H.100 16.384Mbit/s ........................................................................................................................................... 74 Figure 82.: Timing Signals When the Transmit Framer is Running at 12.352 Bit-Multiplexed Mode ............................... 75 Figure 83.: Timing signals when the transmit framer is running at 16.384 Bit-Multiplexed mode .................................... 77 Figure 84.: Timing signals when the transmit framer is running at HMVIP / H.100 16.384MHz Mode ............................ 79 Figure 85.: Interfacing XRT86VL3x Receive to local terminal equipment using 16.384Mbit/s, HMVIP 16.384Mbit/s, and H.100 16.384Mbit/s ........................................................................................................................................... 80 Figure 86.: Waveforms for Connecting the Receive Multiplexed High-Speed Input Interface at 12.352Mbit/s mode ..... 80 Figure 87.: Waveforms for Connecting the Receive Multiplexed High-Speed Input Interface at 16.384Mbit/s mode ..... 80 Figure 88.: Waveforms for Connecting the Receive Multiplexed High-Speed Input Interface at HMVIP and H.100 16.384Mbit/ s mode ............................................................................................................................................................... 81 Figure 89.: Timing Diagram of the TxSig_n Input ............................................................................................................ 83 Figure 90.: Simple Diagram of E1 system model ............................................................................................................. 93 Figure 91.: Generation of Yellow Alarm by the Repeater upon detection of line failure .................................................. 94 Figure 92.: Generation of AIS by the Repeater upon detection of line failure .................................................................. 95 Figure 93.: Generation of Yellow Alarm by the CPE upon detection of AIS originated by the Repeater ......................... 96 Figure 94.: Generation of CAS Multi-frame Yellow Alarm and AIS16 by the Repeater ................................................... 97 Figure 95.: Generation of CAS Multi-frame Yellow Alarm by the CPE upon detection of "AIS16" pattern sent by the Repeater 98 Figure 96.: Simple Diagram of DS1 System Model ....................................................................................................... 101 Figure 97.: Generation of Yellow Alarm by the CPE upon detection of line failure ........................................................ 102 Figure 98.: Generation of Yellow Alarm by the CPE upon detection of AIS originated by the Repeater ....................... 104 Figure 99.: Single E1 Frame Diagram ........................................................................................................................... 108 Figure 100.: Frame/Byte Format of the CAS Multi-Frame Structure .............................................................................. 111 Figure 101.: E1 Frame Format ....................................................................................................................................... 112 Figure 102.: T1 Frame Format ....................................................................................................................................... 113 Figure 103.: T1 Superframe PCM Format ..................................................................................................................... 114
V
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Figure 104.: T1 Extended Superframe Format .............................................................................................................. 115 Figure 105.: T1DM Frame Format ................................................................................................................................. 117 Figure 106.: Framer System Transmit Timing Diagram (Base Rate/Non-Mux) ............................................................. 121 Figure 107.: Framer System Receive Timing Diagram (RxSERCLK as an Output) ...................................................... 122 Figure 108.: Framer System Receive Timing Diagram (RxSERCLK as an Input) ......................................................... 123 Figure 109.: Framer System Transmit Timing Diagram (HMVIP and H100 Mode) ....................................................... 124 Figure 110.: Framer System Receive Timing Diagram (HMVIP/H100 Mode) ............................................................... 125 Figure 111.: Framer System Transmit Overhead Timing Diagram ................................................................................ 126 Figure 112.: Framer System Receive Overhead Timing Diagram (RxSERCLK as an Output) ..................................... 127 Figure 113.: Framer System Receive Overhead Timing Diagram (RxSERCLK as an Input) ........................................ 127 Figure 114.: ITU G.703 Pulse Template ........................................................................................................................ 131 Figure 115.: DSX-1 Pulse Template (normalized amplitude) ........................................................................................ 132 Figure 116.: Intel P Interface Timing During Programmed I/O Read and Write Operations When ALE Is Not Tied 'HIGH' 134 Figure 117.: Intel P Interface Timing During Programmed I/O Read and Write Operations When ALE Is Tied 'HIGH' 135 Figure 118.: Motorola Asychronous Mode Interface Signals During Programmed I/O Read and Write Operations ..... 136 Figure 119.: Power PC 403 Interface Signals During Programmed I/O Read and Write Operations ........................... 137
VI
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
LIST OF TABLES
Table 1:: Bit Ordering and Usage .................................................................................................................................... 26 Table 2:: Framing Format for PMON Status Inserted within LAPD by Initiating APR ...................................................... 27 Table 3:: Random Bit Sequence Polynomials .................................................................................................................. 44 Table 4:: Short Haul Line Build Out ................................................................................................................................. 47 Table 5:: Selecting the Internal Impedance ..................................................................................................................... 49 Table 6:: Mapping a T1 Frame into an E1 Frane ............................................................................................................. 70 Table 7:: Bit Format of Timeslot 0 octet within a FAS E1 Frame ................................................................................... 108 Table 8:: Bit Format of Timeslot 0 octet within a Non-FAS E1 Frame ........................................................................... 109 Table 9:: Bit Format of all Timeslot 0 octets within a CRC Multi-frame .......................................................................... 110 Table 10:: Superframe Format ....................................................................................................................................... 114 Table 11:: Extended Superframe Format ....................................................................................................................... 116 Table 12:: Non-Signaling Framing Format ..................................................................................................................... 117 Table 13:: SLC(R)96 Fs Bit Contents ............................................................................................................................... 118 Table 14:: XRT86VL32 Power Consumption ................................................................................................................ 119 Table 15:: XRT86VL34 Power Consumption ................................................................................................................ 120 Table 16:: XRT86VL38 Power Consumption ................................................................................................................ 120 Table 17:: E1 Receiver Electrical Characteristics .......................................................................................................... 128 Table 18:: T1 Receiver Electrical Characteristics .......................................................................................................... 129 Table 19:: E1 Transmit Return Loss Requirement ......................................................................................................... 129 Table 20:: E1 Transmitter Electrical Characteristics ...................................................................................................... 130 Table 21:: T1 Transmitter Electrical Characteristics ...................................................................................................... 130 Table 22:: Transmit Pulse Mask Specification ............................................................................................................... 131 Table 23:: DSX1 Interface Isolated pulse mask and corner points ................................................................................ 132 Table 24:: AC Electrical Characteristics ......................................................................................................................... 133 Table 25:: Intel Microprocessor Interface Timing Specifications .................................................................................... 134 Table 26:: Intel Microprocessor Interface Timing Specifications .................................................................................... 135 Table 27:: Motorola Asychronous Mode Microprocessor Interface Timing Specifications ............................................. 136 Table 28:: Power PC 403 Microprocessor Interface Timing Specifications ................................................................... 137
VII
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
1.0 GENERAL DESCRIPTION AND INTERFACE The XRT86VL3x supports multiple interfaces for various modes of operation. The purpose of this section is to present a general overview of the common interfaces and their connection diagrams. Each mode will be described in full detail in later sections of the datasheet.
NOTE: For a brief tutorial on Framing Formats, see Appendix A in the back of this document.
1.1
Physical Interface
The Line Interface Unit generates/receives standard return-to-zero (RZ) signals to the line interface for T1/E1/ J1 twisted pair or E1 coaxial cable. The physical interface is optimized by placing the terminating impedance inside the LIU. This allows one bill of materials for all modes of operation reducing the number of external components necessary in system design. The transmitter outputs only require one DC blocking capacitor of 0.68F and a 1:2 step-up transformer. The receive path inputs only require one bypass capacitor of 0.1F connected to the center tap (CT) of the transformer and a 1:1 transformer. The receive CT bypass capacitor is required for Long Haul Applications, and recommended for Short Haul Applications. Figure 2 shows the typical connection diagram for the LIU transmitters. Figure 3 shows a typical connection diagram for the LIU receivers. FIGURE 2. LIU TRANSMIT CONNECTION DIAGRAM USING INTERNAL TERMINATION
XRT86VL3x LIU TTIP Transmitter Output C=0.68uF T RING Line Interface T1/E1/J1 1:2
One Bill of Materials Internal Impedance
FIGURE 3. LIU RECEIVE CONNECTION DIAGRAM USING INTERNAL TERMINATION
XRT86VL3x LIU Receiver Input
RTIP
1:1 Line Interface T1/E1/J1
R RING 0.1F
Internal Impedance
One Bill of Materials
4
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 1.2 R3 Technology (Relayless / Reconfigurable / Redundancy)
REV. 1.2.0
Redundancy is used to introduce reliability and protection into network card design. The redundant card in many cases is an exact replicate of the primary card, such that when a failure occurs the network processor can automatically switch to the backup card. EXAR's R3 technology has re-defined DS-1/E1/J1 physical interface design for 1:1 and 1+1 redundancy applications. Without relays and one Bill of Materials, EXAR offers multi-port, integrated Framer/LIU solutions to assist high density aggregate applications and framing requirements with reliability. The following section can be used as a reference for implementing R3 Technology with EXAR's world leading Framer/LIU combo. 1.2.1 Line Card Redundancy
Telecommunication system design requires signal integrity and reliability. When a T1/E1 primary line card has a failure, it must be swapped with a backup line card while maintaining connectivity to a backplane without losing data. System designers can achieve this by implementing common redundancy schemes with the XRT86VL3x Framer/LIU. EXAR offers features that are tailored to redundancy applications while reducing the number of components and providing system designers with solid reference designs. 1.2.2 Typical Redundancy Schemes
* 1:1 One backup card for every primary card (Facility Protection) * 1+1 One backup card for every primary card (Line Protection) * *N+1 One backup card for N primary cards
1.2.3 1:1 and 1+1 Redundancy Without Relays The 1:1 facility protection and 1+1 line protection have one backup card for every primary card. When using 1:1 or 1+1 redundancy, the backup card has its transmitters tri-stated and its receivers in high impedance. This eliminates the need for external relays and provides one bill of materials for all interface modes of operation. For 1+1 line protection, the receiver inputs on the backup card have the ability to monitor the line for bit errors while in high impedance. The transmit and receive sections of the physical interface are described separately. 1.2.4 Transmit Interface with 1:1 and 1+1 Redundancy
The transmitters on the backup card should be tri-stated. Select the appropriate impedance for the desired mode of operation, T1/E1/J1. A 0.68uF capacitor is used in series with TTIP for blocking DC bias. See Figure 4. for a simplified block diagram of the transmit section for a 1:1 and 1+1 redundancy. FIGURE 4. SIMPLIFIED BLOCK DIAGRAM OF THE TRANSMIT INTERFACE FOR 1:1 AND 1+1 REDUNDANCY
Backplane Interface
Primary Card
XRT86VL3x 1:2 Tx 0.68uF T1/E1 Line
Internal Impedence
Backup Card
XRT86VL3x 1:2 Tx 0.68uF
Internal Impedence
5
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION Receive Interface with 1:1 and 1+1 Redundancy
1.2.5
The receivers on the backup card should be programmed for "High" impedance. Since there is no external resistor in the circuit, the receivers on the backup card will not load down the line interface. This key design feature eliminates the need for relays and provides one bill of materials for all interface modes of operation. Select the impedance for the desired mode of operation, T1/E1/J1. To swap the primary card, set the backup card to internal impedance, then the primary card to "High" impedance. See Figure 5. for a simplified block diagram of the receive section for a 1:1 redundancy scheme. FIGURE 5. SIMPLIFIED BLOCK DIAGRAM OF THE RECEIVE INTERFACE FOR 1:1 AND 1+1 REDUNDANCY
Backplane Interface
Primary Card
XRT86VL3x 1:1 Rx T1/E1 Line
Internal Impedence
Backup Card
XRT86VL3x 1:1 Rx
"High" Impedence
6
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 1.3 Power Failure Protection
REV. 1.2.0
For 1:1 or 1+1 line card redundancy in T1/E1 applications, power failure could cause a line card to change the characteristics of the line impedance, causing a degradation in system performance. The XRT86VL3x was designed to ensure reliability during power failures. The LIU has patented high impedance circuits that allow the receiver inputs and the transmitter outputs to be in "High" impedance when the LIU experiences a power failure or when the LIU is powered off.
NOTE: For power failure protection, a transformer must be used to couple to the line interface. See the TAN-56 application note for more details.
1.4
Overvoltage and Overcurrent Protection
Physical layer devices such as LIUs that interface to telecommunications lines are exposed to overvoltage transients posed by environmental threats. An Overvoltage transient is a pulse of energy concentrated over a small period of time, usually under a few milliseconds. These pulses are random and exceed the operating conditions of CMOS transceiver ICs. Electronic equipment connecting to data lines are susceptible to many forms of overvoltage transients such as lightning, AC power faults and electrostatic discharge (ESD). There are three important standards when designing a telecommunications system to withstand overvoltage transients.
* UL1950 and FCC Part 68 * Telcordia (Bellcore) GR-1089 * ITU-T K.20, K.21 and K.41
NOTE: For a reference design and performance, contact your local sales representative for more details.
1.5
Non-Intrusive Monitoring
In non-intrusive monitoring applications, the transmitters are shut off by setting TxON "Low". The receivers must be actively receiving data without interfering with the line impedance. The XRT86VL3x's internal termination ensures that the line termination meets T1/E1 specifications for 75, 100 or 120 while monitoring the data stream. System integrity is maintained by placing the non-intrusive receiver in "High" impedance, equivalent to that of a 1+1 redundancy application. A simplified block diagram of non-intrusive monitoring is shown in Figure 6. FIGURE 6. SIMPLIFIED BLOCK DIAGRAM OF A NON-INTRUSIVE MONITORING APPLICATION
XRT86VL3x Line Card Transceiver
Data Traffic Node
XRT86VL3x Non-Intrusive Receiver
7
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
1.6
T1/E1 Serial PCM Interface
The most common mode is the standard serial PCM interface. Within this mode, only the serial data, serial clock, frame pulse and multi-frame pulse are required for both the transmit and receive paths. For the transmit path, only TxSER is a dedicated input to the device. All other signals to the transmit path in Figure 7 can be programmed as either input or output. For the receive path, only RxSER and RxMSYNC are dedicated outputs from the device. All other signals in the receive path in Figure 8 can be programmed as either input or output. FIGURE 7. TRANSMIT T1/E1 SERIAL PCM INTERFACE
T1
TxSER
F
TS1
TS2
TS24
TxSERclk (bi-directional) TxSYNC (bi-directional) TxMSYNC (bi-directional) N: SF : T1DM : SLC-96 : ESF : TxMSYNC = 4 * (TxSYNC) TxMSYNC = 12 * (TxSYNC) TxMSYNC = 12 * (TxSYNC) TxMSYNC = 12 * (TxSYNC) TxMSYNC = 24 * (TxSYNC)
E1
TxSER TxSERclk (bi-directional) TxSYNC (bi-directional) TxMSYNC (bi-directional)
TS1
TS2
TS32
TxMSYNC = 16 * (TxSYNC)
FIGURE 8. RECEIVE T1/E1 SERIAL PCM INTERFACE
T1
RxSER
F
TS1
TS2
TS24
RxSERcl k (bi-directional) RxSYNC (bi-directional) RxCRCSYNC N: SF : T1DM : SLC-96 : ESF : RxCRCSYNC = 4 * (RxSYNC) RxCRCSYNC = 12 * (RxSYNC) RxCRCSYNC = 12 * (RxSYNC) RxCRCSYNC = 12 * (RxSYNC) RxCRCSYNC = 24 * (RxSYNC)
E1
RxSER RxSERcl k (bi-directional) RxSYNC (bi-directional) RxCASYNC
TS1
TS2
TS32
RxCASYNC = 16 * (RxSYNC)
8
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 1.7 T1/E1 Fractional Interface
REV. 1.2.0
The individual time slots can be enabled/disabled to carry fractional DS-0 data. The purpose of this interface is to enable one or more time slots in the PCM data (TxSER) to be replaced with the fractional DS-0 payload. If this mode is selected, the dedicated hardware pin TxCHN1/T1FR is used to input the fractional DS-0 data within the time slots that are enabled. The dedicated hardware pin RxCHN1/R1FR is used to output the fractional DS-0 data within the time slots that are enabled. Figure 9 is a simplified diagram of the Fractional Interface. FIGURE 9. T1 FRACTIONAL INTERFACE
TxSER F PCM TS[0-(N-1)] T1 Fractional Data PCM TS[(M+1)-23]
TxCHN1/T1FR TxSERclk TxSYNC TxMSYNC
TSN - TSM
9
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
1.8
T1/E1 Time Slot Substitution and Control
The time slots within PCM data are reserved for carrying individual DS-0's. However, the framer block (transmit or receive paths) can substitute the payload with various code definitions. Each time slot can be independently programmed to carry normal PCM data or a variety of user codes. In E1 mode, the user can substitute the transmit time slots 0 and 16, although signaling and Frame Sync cannot be maintained. The following options for time slot substitution are available:
* Unchanged * Invert all bits * Invert even bits * Invert odd bits * Programmable User Code * Busy 0xFF * Vacant 0xD5 * Busy TS, Busy 00 * A-Law, -Law * Invert the MSB bit * Invert all bits except the MSB bit * PRBS * D/E Channel (or Fractional Input)
FIGURE 10. T1/E1 TIME SLOT SUBSTITUTION AND CONTROL
TSn - TSn+m TxSER TxSERclk TxSYNC TxMSYNC F
PCM Data
Substitution
PCM Data
10
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 1.9 Robbed Bit Signaling/CAS Signaling
REV. 1.2.0
Signaling is used to convey status information relative to the individual DS-0's. If a particular DS-0 is On Hook, Off Hook, etc. this information is carried within the robbed bits in T1 (SF/ESF/SLC-96) or the sixteenth time slot in E1. On the transmit path, the Signaling information can be inserted through the PCM data, internal registers, or a dedicated external Signaling Bus by programming the appropriate registers. On the receive path, the signaling information is extracted (if enabled) to the internal registers and the external signaling bus in addition to being embedded within the PCM data. If the user wishes to substitute the ABCD values, the substitution only occurs in the PCM data. Once substituted, the internal registers and the external signaling bus will not be affected. Figure 11 is a simplified block diagram showing the Signaling Interface. Figure 12 is a timing diagram showing how to insert the ABCD values for each time slot in ESF / CAS. Figure 13 is a timing diagram showing how to insert the AB values for SF / SLC-96 or 4-code signaling in ESF / CAS. FIGURE 11. ROBBED BIT SIGNALING / CAS SIGNALING
TSCR Internal Reg's TxCHN0/ TxSIG
RBS/CAS Transmit Direction PCM Data Tx LIU Physical Interface Signaling Substitution Receive Direction
TxSER
RxSER
PCM Data
Rx LIU
RxCHN0/ RxSIG
Signaling Extraction
RSAR Internal Reg's
FIGURE 12. ESF / CAS EXTERNAL SIGNALING BUS
TxSERclk
TxSER
F
TS 1
TS 2
TS 3
TxCHN0/TxSIG
A
B
C
D
A
B
C
D
A
B
C
D
TxSYNC
TxMSYNC
11
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 13. SF / SLC-96 OR 4-CODE SIGNALING IN ESF / CAS EXTERNAL SIGNALING BUS
TxSERclk
TxSER
F
TS 1
TS 2
TS 3
TxCHN0/TxSIG
A
B
A
B
A
B
TxSYNC
TxMSYNC
1.10
Overhead Interface
The Overhead interface provides an option for inserting the datalink bits into the transmit PCM data or extracting the datalink bits from the receive PCM data. By default, the datalink information is processed to and from the PCM data directly. On the transmit path, the overhead clock is automatically provided as a clock reference to externally time the datalink bits. The user should provide data on the rising edge of the TxOHclk so that the framer can sample the datalink bits on the falling edge. On the receive path, the datalink bits are updated on the rising edge of the RxOHclk output pin. In T1 ESF mode, a datalink bit occurs every other frame. Therefore, the default overhead interface is operating at 4kbps. In E1 mode, the datalink bits are located in the first time slot of each Non-FAS frame. Figure 14 is a simplified block diagram of the Overhead Interface. Figure 15 is a simplified diagram for the T1 external overhead datalink bus. Figure 16 is a simplified diagram for the E1 external overhead datalink bus. FIGURE 14. T1/E1 OVERHEAD INTERFACE
TxOH TxOHclk
Datalink Bits Transmit Direction PCM Data Tx LIU Physical Interface
TxSER
Receive Direction RxSER PCM Data Rx LIU
RxOH RxOHclk
Datalink Bits
12
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 15. T1 EXTERNAL OVERHEAD DATALINK BUS
REV. 1.2.0
TxSYNC TxOHclk (4kHz) TxOH
Frame1
Frame2
Frame3
Frame4
Frame5
Frame6
Datalink Bit
Datalink Bit
Datalink Bit
FIGURE 16. E1 OVERHEAD EXTERNAL DATALINK BUS
TxSYNC
Non-FAS Frame
FAS Frame
TxSER
Si
1
A Sa4 Sa5 Sa6 Sa7 Sa8
TxOHclk If Sa4, Sa7, and Sa8 are Selected
TxOH
Sa4
Sa7 Sa8
13
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
1.11
Framer Bypass Mode
The framer bypass mode allows the XRT86VL3x to be used as a stand alone Line Interface Unit. In this mode, a few of the backplane interface signals multiplex into the digital Input/output signals to and from the LIU block. Figure 22 shows a simplified block diagram of the framer bypass mode. FIGURE 17. SIMPLIFIED BLOCK DIAGRAM OF THE FRAMER BYPASS MODE
TCLK=TxSERCLK TPOS=TxSER TNEG=TxSYNC
Tx Serial Data In
2-Frame Slip Buffer Elastic Store
Tx Framer
Tx LIU Interface
RCLK=RxSERCLK RPOS=RxSER RNEG=RxSYNC
Rx Serial Data Out
2-Frame Slip Buffer Elastic Store
Rx Framer
Rx LIU Interface
14
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 1.12 High-Speed Non-Multiplexed Interface
REV. 1.2.0
The speed of transferring data through a back plane interface in a non-multiplexed manner typically operates at 1.544Mbps, 2.048Mbps, 4.096Mbps, or 8.192Mbps. For 12.352Mbps and 16.384Mbps, see the High-Speed Multiplexed Section. The T1/E1 carrier signal out to or in from the line interface is always 1.544MHz and 2.048MHz respectively. However, the back plane interface may be synchronous to a "Higher" speed clock. For T1, as shown in Figure 18, is mapped into an E1 frame. Therefore, every fourth time slot contains nonvalid data. For E1, as shown in Figure , is simply synchronized to the "Higher" 8.192MHz clock signal supplied to the TxMSYNC input pin.
FIGURE 18. T1 HIGH-SPEED NON-MULTIPLEXED INTERFACE
Non-Multiplexed High Speed Interface (2.048MHz/4.096MHz/8.192MHz)
TxMSYNC 2.048MHz
TxSER TxSERCLK (1.544MHz) TxSYNC
F
Don't Care
TS 1
TS 2
TS 3
Don't Care
TS 4
TS 5
FIGURE 19. E1 HIGH-SPEED NON-MULTIPLEXED INTERFACE
Non-Multiplexed High Speed Interface (2.048MHz/4.096MHz/8.192MHz)
TxMSYNC (8.192MHz)
TxSER TxSERCLK (2.048MHz) TxSYNC
TS 1
TS 2
TS 3
15
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
1.13
High-Speed Multiplexed Interface
In addition to the non-multiplexed mode, the framer can interface through the backplane in a high-speed multiplexed application, either through a bit-muxed or byte-muxed (in HMVIP or H.100) manner. In this mode, the chip is divided into two multiplexed blocks, four channels per block. For T1, the high speed multiplexed modes are 12.352Mbps (bit-muxed, TxSYNC is "High" during the F-bit), 16.384Mbps (bit-muxed, TxSYNC is "High" during the F-bit), 16.384Mbps (HMVIP: byte-muxed, TxSYNC is "High" during the last 2-bits of the previous frame and the first 2-bits of the current frame), or 16.384Mbps (H.100: byte-muxed, TxSYNC is "High" during the last bit of the previous frame and the first bit in the current frame). For E1 mode, the only mode that is not supported is the 12.352Mbps. The only other difference is that the F-bit (for T1 mode) becomes the first bit of the E1 frame. Figure 20 is a simplified block diagram of transmit bit-muxed application. Figure 21 is a simplified block diagram of receive bit-muxed application. Although the data is only applied to channel 4 or channel 0, the TxSERCLK is necessary for all channels so that the transmit line rate is always equal to the T1/ E1 carrier rate.
FIGURE 20. TRANSMIT HIGH-SPEED BIT MULTIPLEXED BLOCK DIAGRAM
TxSYNC4 TxMSYNC4 (16.384MHz) 5b2 5b1 5b0 TxSER4 7b2 7b2 6b2 6b2 5b2 5b2 4b2 4b2 7b1 7b1 6b1 6b1 5b1 5b1 4b1 4b1 7b0 7b0 6b0 6b0 5b0 5b0 4b0 4b0 TxSERCLK4 (2.048MHz) 7b2 7b1 7b0 TxSERCLK5 (2.048MHz) TxSERCLK6 (2.048MHz) TxSERCLK7 (2.048MHz) TTIP/TRing7 DMUX 6b2 6b1 6b0 TTIP/TRing6 TTIP/TRing5 Bit Interleaved Multiplexed Mode 4b2 4b1 4b0 TTIP/TRing4
FIGURE 21. RECEIVE HIGH-SPEED BIT MULTIPLEXED BLOCK DIAGRAM
RxSYNC4 RxSERCLK4 (16.384MHz) 5b0 5b1 5b2 RxSER4 4b0 0 5b0 0 6b0 0 7b0 0 4b1 0 5b1 0 6b1 0 7b1 0 4b2 0 5b2 0 6b2 0 7b2 0 RZ Data RxLineClk4 (2.048MHz) 7b0 7b1 7b2 RxLineClk5 (2.048MHz) RxLineClk6 (2.048MHz) RxLineClk7 (2.048MHz) RTIP/RRing7 MUX 6b0 6b1 6b2 RTIP/RRing6 RTIP/RRing5 Bit Interleaved Multiplexed Mode 4b0 4b1 4b2 RTIP/RRing4
16
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 2.0 LOOPBACK MODES OF OPERATION 2.1 LIU Physical Interface Loopback Diagnostics
REV. 1.2.0
The XRT86VL3x supports several loopback modes for diagnostic testing. The following section describes the local analog loopback, remote loopback, digital loopback, and dual loopback modes. The LIU physical interface loopback modes are independent from the Framer loopback modes. Therefore, it is possible to configure multiple loopback modes creating tremendous flexibility within the looped diagnostic features.
2.1.1 Local Analog Loopback
With local analog loopback activated, the transmit output data at TTIP/TRING is internally looped back to the analog inputs at RTIP/RRING. External inputs at RTIP/RRING are ignored while valid transmit output data continues to be sent to the line. A simplified block diagram of local analog loopback is shown in Figure 22.
FIGURE 22. SIMPLIFIED BLOCK DIAGRAM OF LOCAL ANALOG LOOPBACK
NLC/PRBS/QRSS TCLK TPOS TNEG Timing Control
TAOS TTIP TRING
Encoder
JA
Tx
RCLK RPOS RNEG
Decoder
JA
Data and Clock Recovery
Rx
RTIP RRING
NOTE: The transmit diagnostic features such as TAOS, NLC generation, and QRSS take priority over the transmit input data at TCLK/TPOS/TNEG.
2.1.2
Remote Loopback
With remote loopback activated, the receive input data at RTIP/RRING is internally looped back to the transmit output data at TTIP/TRING. The remote loopback includes the Receive JA (if enabled). The transmit input data at TCLK/TPOS/TNEG are ignored while valid receive output data continues to be sent to the system. A simplified block diagram of remote loopback is shown in Figure 23.
FIGURE 23. SIMPLIFIED BLOCK DIAGRAM OF REMOTE LOOPBACK
NLC/PRBS/QRSS TCLK TPOS TNEG Timing Control
TAOS
Encoder
JA
Tx
TTIP TRING
RCLK RPOS RNEG
Decoder
JA
Data and Clock Recovery
Rx
RTIP RRING
17
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION Digital Loopback
2.1.3
With digital loopback activated, the transmit input data at TCLK/TPOS/TNEG is looped back to the receive output data at RCLK/RPOS/RNEG. The digital loopback mode includes the Transmit JA (if enabled). The receive input data at RTIP/RRING is ignored while valid transmit output data continues to be sent to the line. A simplified block diagram of digital loopback is shown in Figure 24.
FIGURE 24. SIMPLIFIED BLOCK DIAGRAM OF DIGITAL LOOPBACK
NLC/PRBS/QRSS TCLK TPOS TNEG Timing Control
TAOS
Encoder
JA
Tx
TTIP TRING
RCLK RPOS RNEG
Decoder
JA
Data and Clock Recovery
Rx
RTIP RRING
2.1.4
Dual Loopback
With dual loopback activated, the remote loopback is combined with the digital loopback. A simplified block diagram of dual loopback is shown in Figure 25.
FIGURE 25. SIMPLIFIED BLOCK DIAGRAM OF DUAL LOOPBACK
NLC/PRBS/QRSS TCLK TPOS TNEG Timing Control
TAOS
Encoder
JA
Tx
TTIP TRING
RCLK RPOS RNEG
Decoder
JA
Data and Clock Recovery
Rx
RTIP RRING
18
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 2.1.5 Framer Remote Line Loopback
REV. 1.2.0
The Framer Remote Line Loopback is almost identical to the LIU physical interface Remote Loopback. The digital data enters the framer interface, however does not enter the framing blocks. The main difference between the Remote loopback and the Framer Remote Line loopback is that the receive digital data from the LIU is allowed to pass through the LIU Decoder/Encoder circuitry before returning to the line interface. A simplified block diagram of framer remote line loopback is shown in Figure 26.
FIGURE 26. SIMPLIFIED BLOCK DIAGRAM OF THE FRAMER REMOTE LINE LOOPBACK
NLC/PRBS/QRSS Framer Tx Timing Control
TAOS
Encoder
JA
Tx
TTIP TRING
Framer Rx
Decoder
JA
Data and Clock Recovery
Rx
RTIP RRING
2.1.6
Framer Local Loopback
With framer local loopback activated, the transmit PCM input data is looped back to the receive PCM output data. The receive input data at RTIP/RRING is ignored while an All Ones Signal is transmitted out to the line interface. A simplified block diagram of framer remote line loopback is shown in Figure 27.
FIGURE 27. SIMPLIFIED BLOCK DIAGRAM OF THE FRAMER LOCAL LOOPBACK
Tx Serial Data In ST-BUS
Tx Serial Clock
2-Frame Slip Buffer Elastic Store
Tx Framer
Tx LIU Interface LLB
Rx Serial Data Out
Rx Serial Clock
2-Frame Slip Buffer Elastic Store
Rx Framer
Rx LIU Interface
19
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
HDLC CONTROLLERS AND LAPD MESSAGES
The purpose of the HDLC controllers is to allow messages to be stored for transport in the outbound transmit framer block or extracted from the receive framer block through the LAPD interface. Each channel within the Framer has 3 independent HDLC controllers. Each HDLC controller has two 96-Byte buffers for Transmit and two 96-Byte buffers for Receive. The buffers are used to insert messages into the out going data stream for Transmit or to extract messages from the incoming data stream from the Receive path. Total, there are twelve 96-Byte buffers per channel. This allows multiple HDLC messages to be transported to and from EXAR's framing device.
FIGURE 28. HDLC CONTROLLERS
Channel N
Buffer 0 Transmit Receive 96-Bytes 96-Bytes
Buffer 1 96-Bytes HDLC1 96-Bytes
Buffer 0 Transmit Receive 96-Bytes 96-Bytes
Buffer 1 96-Bytes HDLC2 96-Bytes
Buffer 0 Transmit Receive 96-Bytes 96-Bytes
Buffer 1 96-Bytes HDLC3 96-Bytes
2.2
Programming Sequence for Sending Less Than 96-Byte Messages
Once the data link source and the type of message has been chosen, the following programming sequence can be followed to send (in this example) a 15-bye LAPD message.
NOTE: To send more than 96-Bytes, the programming sequence is slightly modified, which is described in the next section. 1. Read the Transmit Data Link Byte Count Register to determine which buffer is available. 2. Enable TxSOT in the Data Link Interrupt Enable Register. 3. Write 0x0F into the transmit byte count register (assuming buffer 0 was available). 4. Write the 15-byte message contents into register 0xn600 (automatically incremented). 5. Enable the LAPD transmission by writing to register 0xn113. 6. Once TxEOT occurs, the message has been transmitted.
2.3
Programming Sequence for Sending Large Messages
1. Read the Transmit Data Link Byte Count Register to determine which buffer is available. 2. Enable TxSOT in the Data Link Interrupt Enable Register. 3. Write 0x60 into the transmit byte count register (assuming buffer 0 was available). 4. Write the first 96-bytes into register 0xn600 (buffer 0, automatically incremented). 5. Enable the LAPD transmission by writing to register 0xn113. 6. Wait for the TxSOT before writing the next 96-bytes.
20
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
7. Re-initiate the TxSOT interrupt enable. 8. Write 0xE0 into the transmit byte count register (buffer 1). 9. Write the next 96-bytes into 0xn700 (buffer 1, automatically incremented). 10. Enable the LAPD transmission by writing to register 0xn113. 11. Wait for the TxSOT before writing the next 96-bytes. 12. Continue until the entire message is sent.
REV. 1.2.0
2.4
Programming Sequence for Receiving LAPD Messages
The XRT86VL3x can extract data link information from incoming DS1 frames from either the datalink bits themselves or the D/E time slots within the PCM input data. To extract a LAPD message, the following programming sequence can be used as a reference.
1. Enable RxEOT in the Data Link Interrupt Enable Register. 2. Wait for the RxEOT interrupt to occur. 3. Once RxEOT occurs, read the Receive Data Link Byte Count Register to determine which buffer the data is
extracted to and how many bytes are contained within the message.
4. Read the exact amount of bytes from the proper buffer. If buffer 0, read 0xn600. If buffer 1, read 0xn700. These
two registers are automatically incremented.
2.5
SS7 (Signaling System Number 7) for ESF in DS1 Only
To support SS7 specifications while receiving LAPD messages, EXAR's Framer will generate an interrupt (if SS7 is enabled) once the HDLC controllers have received more than 276 bytes within two flag sequences (0x7E) of a LAPD message. Each HDLC controller supports SS7. For example: To enable SS7 for all HDLC controllers, registers 0xnB11 (LAPD1), 0xnB19 (LAPD2), 0xnB29 (LAPD3) must be set to 0x01.
2.6 DS1/E1 Datalink Transmission Using the HDLC Controllers
The transmit framer block can insert data link information to outbound DS1/E1 frames. The data link information can be inserted from the following sources.
* Transmit Overhead Input Interface (TxOH) * Transmit HDLC1 Controller * Transmit Serial Input Interface (TxSER)
NOTE: HDLC1 is the dedicated controller for transmission of LAPD messages through the datalink bits. If the datalink bits are not used for LAPD messages, then HDLC1 can be used through the D/E time slots as with HDLC2 and HDLC3.
The Transmit Data Link Source Select bits within the Transmit Data Link Select Register (TSDLSR) determine the source for the data link bits in ESF, SLC(R)96, or T1DM for DS1 and CRC multi frame for E1. Each Transmit HDLC Controller contains four major functional modules.
* Bit-Oriented Signaling Processor * LAPD Controller * SLC(R)96 Data Link Controller * Automatic Performance Report (APR) Generation
2.7 Transmit BOS (Bit Oriented Signaling) Processor
The Transmit BOS Processor handles transmission of BOS messages through the data link channel. The processor can be set for a specific amount of repetitions a certain BOS message will be transmitted, or it may be placed in an infinite loop. The processor can also insert a BOS IDLE flag sequence and/or an ABORT sequence to be transmitted on the data link channel.
2.7.1 Description of BOS
21
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Bit-Oriented Signaling messages are a 16-bit pattern of which a 6-bit message is embedded as shown in the following table.
BOS MESSAGE FORMAT
0
D5
D4
D3
D2
D1
D0
0
1
1
1
1
1
1
1
1
Where D5 is the MSB and D0 is the LSB. The rightmost "1" is transmitted first. BOS is classified into the following two groups.
* Priority Codeword Message * Command and Response Information
2.7.2 Priority Codeword Message
A Priority Codeword Message is preemptive and has the highest priority among all data link information. A Priority Codeword indicates a condition that is affecting the quality of service and thus shall be transmitted until the condition no longer exists. The duration of transmission should not be less than one second. A priority codeword may be interrupted by software for 100 milliseconds to send maintenance commands with a minimum interval of one second between interruptions. Yellow alarm (00000000 11111111) is the only priority message defined in industry standards.
2.7.3 Command and Response Information
Command and Response Information is transmitted to perform various functions. The BOS Processor can send a command and response by transmitting a minimum of 10 repetitions of the appropriate codeword pattern. A Command and response data transmission initiates action at the remote end, while the remote end will respond by sending Bit-Oriented response message to acknowledge the received commands. The activation and deactivation of line remote loop-back and local payload loop-back functions are of this type.
2.8 Transmit MOS (Message Oriented Signaling) Processor
The Transmit LAPD controller implements the Message-Oriented protocol based on ITU Recommendation Q.921 Link Access Procedures on the D-channel. It provides the following functions.
* Zero stuffing * T1/E1 transmitter interface * Transmit message buffer access * Frame check sequence generation * IDLE flag insertion * ABORT sequence generation
Two 96-byte buffers in shared memory are allocated for each LAPD to reduce the frequency of microprocessor interrupts and alleviate the response time requirement for a microprocessor to handle each interrupt. There are no restrictions on the length of the message. However the 96-byte buffer is deep enough to hold one entire LAPD path or test signal identification message.
2.8.1 Discussion of MOS
Message-Oriented signals sent by the transmit LAPD Controller are messages conforming to ITU Recommendation Q.921 LAPD protocol. There are two types of Message-Oriented signals. One is a periodic performance report generated by the source or sink T1/E1 terminals as defined by ANSI T1.403. The other is a path or test signal identification message that may be optionally generated by a terminal or intermediate equipment on a T1/E1 circuit. The message structures of the performance report and path or test signal identification message are shown in Figure 29 for format A and format B respectively.
22
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 29. LAPD FRAME STRUCTURE
REV. 1.2.0
2.8.2
Periodic Performance Report
The ANSI T1.403 standard requires that the status of the transmission quality be reported in one-second intervals. The one-second timing may be derived from the DS1 signal or from a separate equally accurate (32ppm) source. The phase of the one-second periods does not depend on the time of occurrence of any error event. A total of four seconds of information is transmitted so that recovery operations may be initiated in case an error corrupts a message. Counts of events shall be accumulated in each contiguous one-second interval. At the end of each one-second interval, a modulo-4 counter shall be incremented, and the appropriate performance bits shall be set in bytes 5 and 6 in Format A. These octets and the octets that carry the performance bits of the preceding three one-second intervals form the periodic performance report. The periodic performance report is made up of 14 bytes of data. Bytes 1 to 4, 13, and 14 are the message header and bytes 5 to 12 contain data regarding the four most-recent one-second intervals. The periodic performance report message uses the SAPI/TEI value of 0x14.
2.8.3 Transmission-Error Event
Occurrences of transmission-error events indicate the quality of transmission. The occurrences that shall be detected and reported are:
* CRC Error Event: A CRC-6 error event is the occurrence of a received CRC code that is not identical to the
corresponding locally calculated code.
* Severely Errored Framing Event: A severely-errored-framing event is the occurrence of two or more framingbit-pattern errors within a 3-ms period. Contiguous 3-ms intervals shall be examined. The 3-ms period may coincide with the ESF. The severely-errored-framing event, while similar in form to criteria for declaring a
23
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
terminal has lost framing, is only designed as a performance indicator; existing terminal out-of-frame criteria will continue to serve as the basis for terminal alarms.
* Frame-Synchronization-Bit Error Event: A frame-synchronization-bit-error event is the occurrence of a
received framing-bit-pattern not meeting the severely-errored-framing event criteria.
* Line-Code Violation event: A line-code violation event is a bipolar violation of the incoming data. A line-code
violation event for an B8ZS-coded signal is the occurrence of a received excessive zeros (EXZ) or a bipolar violation that is not part of a zero-substitution code.
* Controlled Slip Event: A controlled-slip event is a replication, or deletion, of a T1 frame by the receiving
terminal. A controlled slip may occur when there is a difference between the timing of a synchronous receiving terminal and the received signal.
2.8.4 Path and Test Signal Identification Message
The path identification message is used to identify the path between the source terminal and the sink terminal. The test signal identification message is used by test signal generating equipment. Both identification messages are made up of 82 bytes of data. Byte 1 to 4, 81 and 82 are the message header and bytes 5 to 80 contain six data elements. These messages use the SAPI/TEI value of 0x15 to differentiate themselves from the performance report message.
2.8.5 Frame Structure
The message structure of message-oriented signal is shown in Figure 29. Two format types are shown in the figure: format A for frames which are sending performance report message and format B for frames which containing a path or test signal identification message. The following abbreviations are used:
* SAPI: Service Access Point Identifier * C/R: Command or Response * EA: Extended Address * TEI: Terminal Endpoint Identifier * FCS: Frame Check Sequence
2.8.6 Flag Sequence
All frames shall start and end with the flag sequence consisting of one 0 bit followed by six contiguous 1 bits and one 0 bit. The flag preceding the address field is defined as the opening flag. The flag following the Frame Check Sequence (FCS) field is defined as the closing flag. The closing flag may also serve as the opening flag of the next frame, in some applications. However, all receivers must be able to accommodate receipt of one or more consecutive flags.
2.8.7 Address Field
The address field consists of two octets. A single octet address field is reserved for LAPB operation in order to allow a single LAPB data link connection to be multiplexed along with LAPD data link connections.
2.8.8 Address Field Extension bit (EA)
The address field range is extended by reserving bit 1 of the address field octets to indicate the final octet of the address field. The presence of a 1 in bit 1 of an address field octet signals that it is the final octet of the address field. The double octet address field for LAPD operation shall have bit 1 of the first octet set to a 0 and bit 1 of the second octet set to 1.
2.8.9 Command or Response bit (C/R)
The Command or Response bit identifies a frame as either a command or a response. The user side shall send commands with the C/R bit set to 0, and responses with the C/R bit set to 1. The network side shall do the opposite; That is, commands are sent with C/R bit set to 1, and responses are sent with C/R bit set to 0.
24
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 2.8.10 Service Access Point Identifier (SAPI)
REV. 1.2.0
The Service Access Point Identifier identifies a point at which data link layer services are preceded by a data link layer entity type to a layer 3 or management entity. Consequently, the SAPI specifies a data link layer entity type that should process a data link layer frame and also a layer 3 or management entity, which is to receive information carried by the data link layer frame. The SAPI allows 64 service access points to be specified, where bit 3 of the address field octet containing the SAPI is the least significant binary digit and bit 8 is the most significant. SAPI values are 0x14 and 0x15 for performance report message and path or test signal identification message respectively.
2.8.11 Terminal Endpoint Identifier (TEI)
The TEI sub-field allows 128 values where bit 2 of the address field octet containing the TEI is the least significant binary digit and bit 8 is the most significant binary digit. The TEI sub-field bit pattern 111 1111 (=127) is defined as the group TEI. The group TEI is assigned permanently to the broadcast data link connection associated with the addressed Service Access Point (SAP). TEI values other than 127 are used for the pointto-point data link connections associated with the addressed SAP. Non-automatic TEI values (0-63) are selected by the user, and their allocation is the responsibility of the user. The network automatically selects and allocates TEI values (64-126).
2.8.12 Control Field
The control field identifies the type of frame which will be either a command or response. The control field shall consist of one or two octets. Three types of control field formats are specified: 2-octet numbered information transfer (I format), 2-octet supervisory functions (S format), and single-octet unnumbered information transfers and control functions (U format). The control field for T1/E1 message is categorized as a single-octet unacknowledged information transfer having the value 0x03.
2.8.13 Frame Check Sequence (FCS) Field
The source of either the performance report or an identification message shall generate the frame check sequence. The FCS field shall be a 16-bit sequence. It shall be the ones complement of the sum (modulo 2) of:
* The remainder of xk (x15 + x14 + x13 + x12 + x11 + x10 + x9 + x8 + x7 + x6 + x5 + x4 + x3 + x2 + x + 1)
divided (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, where k is the number of bits in the frame existing between, but not including, the final bit of the opening flag and the first bit of the FCS, excluding bits inserted for transparency, and
* The remainder of the division (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, of the product of
x16 by the content of the frame existing between, but not including, the final bit of the opening flag and the first bit of the FCS, excluding bits inserted for transparency. As a typical implementation at the transmitter, the initial content of the register of the device computing the remainder of the division is preset to all 1s and is then modified by division by the generator polynomial on the address, control and information fields; the ones complement of the resulting remainder is transmitted as the 16-bit FCS. As a typical implementation at the receiver, the initial content of the register of the device computing the remainder is preset to all 1s. The final remainder, after multiplication by x16 and then division (modulo 2) by the generator polynomial x16 + x12 + x5 + 1 of the serial incoming protected bits and the FCS, will be 0001110100001111 (x15 through x0, respectively) in the absence of transmission errors.
2.8.14 Transparency (Zero Stuffing)
A transmitting data link layer entity shall examine the frame content between the opening and closing flag sequences, (address, control, information and FCS field) and shall insert a 0 bit after all sequences of five contiguous 1 bits (including the last five bits of the FCS) to ensure that an IDLE flag or an Abort sequence is not simulated within the frame. A receiving data link layer entity shall examine the frame contents between the opening and closing flag sequences and shall discard any 0 bit which directly follows five contiguous 1 bits.
25
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
2.9
Transmit SLC(R)96 Data link Controller
The SLC(R)96 T1 format is invented by AT&T and is used between the Digital Switch and a SLC(R)96 formatted remote terminal. The purpose of the SLC(R)96 product is to provide standard telephone service or Plain Old Telephone Service (POTS) in areas of high subscriber density but back-haul the traffic over T1 facilities. To support the SLC(R)96 formatted remote terminal equipment, which is likely in an underground location, the T1 framer must:
* Indicate equipment failures of the equipment to maintenance personal * Indicate failures of the POTS lines * Test the POTS lines * Provide redundancy on the T1s
The SLC(R)96 framing format is a D4 Super-frame (SF) format with specialized data link information bits. These data link information bits take the position of the Super-frame Alignment (Fs) bit positions. These bits consist of the following.
* Concentrator bits (C, bit position 1 to 11) * First Spoiler bits (FS, bit position 12 to 14) * Maintenance bits (M, bit position 15 to 17) * Alarm bits (A, bit position 18 to 19) * Protection Line Switch bits (S, bit position 20 to 23) * Second Spoiler bit (SS, bit position 24) * Resynchronization pattern (000111000111)
In SLC(R)96 mode, a six 6-bit datalink message will generate a one 9-ms frame of the SLC(R)96 message format. The format of the datalink message is given in BELLCORE TR-TSY-000008. When SLC(R)96 mode is enabled, the Fs bit is replaced by the data link message read from memory at the beginning of each D4 superframe. The XRT86VL3x allocates two 6-byte buffers to provide the SLC(R)96 Data Link Controller an alternating access mechanism for information transmission. The bit ordering and usage is shown in the following table; and the LSB is sent first. Note that these registers are memory-based storage and they need to be initialized.
TABLE 1: BIT ORDERING AND USAGE
BYTE 5 4 3 2 1 0
1 2 3 4 5 6
0 C1 C7 1 A2 0
1 1 C6 0 A1 1
1 1 C5 C11 M3 S4
1 1 C4 C10 M2 S3
0 0 C3 C9 M1 S2
0 0 C2 C8 0 S1
Each register is read out of memory once every six SF super-frames. The memory holding these registers owns a shared memory structure that is used by multiple devices. These include DS1 transmit module, DS1 receive module, Transmit LAPD Controller, Transmit SLC(R)96 Data Link controller, Bit-Oriented Signaling Processor, Receive LAPD Controller, Receive SLC(R)96 Data Link Controller, Receive Bit-Oriented Signaling Processor and microprocessor interface module.
26
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 2.10 D/E Time Slot Transmit HDLC Controller Block V5.1 or V5.2 Interface
REV. 1.2.0
V5.2 protocol specifies a provision for transmitting simultaneous LAPD messages. Since only one message can be sent through the datalink bits at one time, an alternative path for communication is offered within the framer block. This alternative path is known as D or E channel which can be transmitted through one or more of the DS-0 time slots. D channel is used primarily for data link applications. E channel is used primarily for signaling for circuit switching with multiple access configurations. A range of time slots can be dedicated to HDLC1, while a different range of time slots can be dedicated to HDLC2 to support V5.2. In addition, HDLC3 can be used to transmit a third LAPD message if desired. The HDLC controllers are implemented in the same manner as the datalink described above with the exception of the data link source select bits.
2.11 Automatic Performance Report (APR)
The APR feature allows the system to transmit PMON status within a LAPD Framing format A at one second intervals or within a single shot report. The data octets 5 through 12 within the LAPD frame are replaced with the PMON status for the previous one second interval.
TABLE 2: FRAMING FORMAT FOR PMON STATUS INSERTED WITHIN LAPD BY INITIATING APR
Octet Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 8 7 5 4 3 Flag = 01111110 SAPI = 001110 TEI = 0000000 Control = 00000011 = Unacknowledged Frame G4 U1 U2 G5 LB G1 R G2 G4 U1 U2 G5 LB G1 R G2 G4 U1 U2 G5 LB G1 R G2 G4 U1 U2 G5 LB G1 R G2 FCS FCS Flag = 01111110 6 2 CR 1 EA=0 EA=1 G6 Ni G6 Ni G6 Ni G6 Ni T0 T0 - 1 T0 - 2 T0 - 3 Time (s)
G3 FE G3 FE G3 FE G3 FE
LV SE LV SE LV SE LV SE
SL Nm SL Nm SL Nm SL Nm
NOTE: The right most bit (bit 1) is transmitted first for all fields except for the two bytes of the FCS that are transmitted left most bit (bit 8) first.
2.11.1
Bit Value Interpretation
G1 = 1 if number of CRC error events is equal to 1 G2 = 1 if number of CRC error events is greater than 1 or equal to 5 G3 = 1 if number of CRC error events is greater than 5 or equal to 10 G4 = 1 if number of CRC error events is greater than 10 or equal to 100 G5 = 1 if number of CRC error events is greater than 100 or equal to 319 G6 = 1 if number of CRC error events is equal to 320 SE = 1 if a severely errored framing event occurs (FE shall be 0) FE = 1 if a framing synchronization bit error event occurs (SE shall be 0) LV = 1 if a line code violation event occurs SL = 1 if slip event within the slip buffer occurs
27
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
LB = 1 if payload loopback is activated U1 = Not Used (default = 0) U2 = Not Used (default = 0) R = Not Used (default = 0) NmNi = One second report module 4 count
28
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 3.0 OVERHEAD INTERFACE BLOCK
REV. 1.2.0
The XRT86VL3x has the ability to extract or insert DS1 data link information from or into the following:
* Facility Data Link (FDL) bits in ESF framing format mode * Signaling Framing (Fs) bits in SLC(R)96 and N framing format mode * Remote Signaling (R) bits in T1DM framing format mode
The source and destination of these inserted and extracted data link bits would be from either the internal HDLC Controller or the external device accessible through DS1 Overhead Interface Block. The operation of the Transmit Overhead Input Interface Block and the Receive Overhead Output Interface Block will be discussed separately.
3.1 3.1.1 DS1 Transmit Overhead Input Interface Block Description of the DS1 Transmit Overhead Input Interface Block
The DS1 Transmit Overhead Input Interface Block will allow an external device to be the provider of the Facility Data Link (FDL) bits in ESF framing format mode, Signaling Framing (Fs) bits in the SLC96 and N framing format mode and Remote Signaling (R) bit in T1DM framing format mode. This interface provides interface signals and required interface timing to shift in proper data link information at proper time. The Transmit Overhead Input Interface for a given Framer consists of two signals.
* TxOHClk_n: The Transmit Overhead Input Interface Clock Output signal * TxOH_n: The Transmit Overhead Input Interface Input signal.
The Transmit Overhead Input Interface Clock Output pin (TxOHCLK_n) generates a rising clock edge for each data link bit position according to configuration of the framer. The Data Link equipment interfaced to the Transmit Overhead Input Interface block should update the data link bits on the TxOH_n line upon detection of the rising edge of TxOHClk_n. The Transmit Overhead Input Interface block will sample and latch the data link bits on the TxOH_n line on the falling edge of TxOHClk_n. The data link bits will be included and transmitted via the outgoing DS1 frames. The figure below shows block diagram of the DS1 Transmit Overhead Input Interface of XRT86VL3x.
FIGURE 30. BLOCK DIAGRAM OF THE DS1 TRANSMIT OVERHEAD INPUT INTERFACE OF THE XRT86VL3X
TxOH_n TxOHClk_n
Transmit Overhead Input Interface
To Transmit Framer Block
3.1.2
Configure the DS1 Transmit Overhead Input Interface module as source of the Facility Data Link (FDL) bits in ESF framing format mode
The FDL bits in ESF framing format mode can be inserted from:
* DS1 Transmit Overhead Input Interface Block * DS1 Transmit HDLC Controller * DS1 Transmit Serial Input Interface.
29
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR) controls the insertion of data link bits into the FDL bits in ESF framing format mode. The table below shows configuration of the Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1-0
Transmit Data Link Source Select
R/W
00 - The Facility Data Link bits are inserted into the framer through either the LAPD controller or the SLC(R)96 buffer. 01 - The Facility Data Link bits are inserted into the framer through the Transmit Serial Data input Interface via the TxSer_n pins. 10 - The Facility Data Link bits are inserted into the framer through the Transmit Overhead Input Interface via the TxOH_n pins. 11 - The Facility Data Link bits are forced to one by the framer.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Transmit Overhead Input Interface Block becomes input source of the FDL bits. The XRT86VL3x allows the user to select bandwidth of the Facility Data Link Channel in ESF framing format mode. The FDL can be either a 4KHz or 2KHz data link channel. The Transmit Data Link Bandwidth Select bits of the Transmit Data Link Select Register (TDLSR) determine the bandwidth of FDL channel in ESF framing format mode. The table below shows configuration of the Transmit Data Link Bandwidth Select bits of the Transmit Data Link Select Register (TDLSR).)
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
5-4
Transmit Data Link Bandwidth Select
R/W
00 - The Facility Data Link is a 4KHz channel. All available FDL bits (first bit of every other frame) are used as data link bits. 01 - The Facility Data Link is a 2KHz channel. Only the odd FDL bits (first bit of frame 1, 5, 9...) are used as data link bits. 10 - The Facility Data Link is a 2KHz channel. Only the even FDL bits (first bit of frame 3, 7, 11...) are used as data link bits.
Figure 31 below shows the timing diagram of the input and output signals associated with the DS1 Transmit Overhead Input Interface module in ESF framing format mode.
30
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 31. DS1 TRANSMIT OVERHEAD INPUT INTERFACE TIMING IN ESF FRAMING FORMAT MODE
REV. 1.2.0
3.1.3
Configure the DS1 Transmit Overhead Input Interface module as source of the Signaling Framing (Fs) bits in N or SLC(R)96 framing format mode
The Fs bits in SLC(R)96 and N framing format mode can be inserted from:
* DS1 Transmit Overhead Input Interface Block * DS1 Transmit HDLC Controller * DS1 Transmit Serial Input Interface.
The Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR) controls the insertion of data link bits into the Fs bits in N or SLC(R)96 framing format mode. The table below shows configuration of the Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1-0
Transmit Data Link Source Select
R/W
00 - The Signaling Framing bits are inserted into the framer through either the LAPD controller or the SLC(R)96 buffer. 01 - The Signaling Framing bits are inserted into the framer through the Transmit Serial Data input Interface via the TxSer_n pins. 10 - The Signaling Framing bits are inserted into the framer through the Transmit Overhead Input Interface via the TxOH_n pins. 11 - The Signaling Framing bits are forced to one by the framer.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Transmit Overhead Input Interface Block becomes input source of the Fs bits.
31
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Figure 32 below shows the timing diagram of the input and output signals associated with the DS1 Transmit Overhead Input Interface module in N or SLC(R)96 framing format mode. FIGURE 32. DS1 TRANSMIT OVERHEAD INPUT TIMING IN N OR SLC(R)96 FRAMING FORMAT MODE
3.1.4
Configure the DS1 Transmit Overhead Input Interface module as source of the Remote Signaling (R) bits in T1DM framing format mode
The R bits in T1DM framing format mode can be inserted from:
* DS1 Transmit Overhead Input Interface Block * DS1 Transmit HDLC Controller * DS1 Transmit Serial Input Interface.
The Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR) controls the insertion of data link bits into the R bits in T1DM framing format mode. The table below shows configuration of the Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1-0
Transmit Data Link Source Select
R/W
00 - The Remote Signaling bits are inserted into the framer through either the LAPD controller or the SLC(R)96 buffer. 01 - The Remote Signaling bits are inserted into the framer through the Transmit Serial Data input Interface via the TxSer_n pins. 10 - The Remote Signaling bits are inserted into the framer through the Transmit Overhead Input Interface via the TxOH_n pins. 11 - The Remote Signaling bits are forced to one by the framer.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Transmit Overhead Input Interface Block becomes input source of the R bits. Since R bit presents in Timeslot 24 of every T1DM frame, therefore, bandwidth of T1DM data link channel is 8KHz.
Figure 33 below shows the timing diagram of the input and output signals associated with the DS1 Transmit Overhead Input Interface module in T1DM framing format mode. FIGURE 33. DS1 TRANSMIT OVERHEAD INPUT INTERFACE MODULE IN T1DM FRAMING FORMAT MODE
32
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 3.2 3.2.1 DS1 Receive Overhead Output Interface Block Description of the DS1 Receive Overhead Output Interface Block
REV. 1.2.0
The DS1 Receive Overhead Output Interface Block allows an external device to be the consumer of the Facility Data Link (FDL) bits in ESF framing format mode, Signaling Framing (Fs) bits in the SLC96 and N framing format mode and Remote Signaling (R) bit in T1DM framing format mode This interface provides interface signals and required interface timing to shift out proper data link information at proper time. The Receive Overhead Output Interface for a given Framer consists of two signals.
* RxOHClk_n: The Receive Overhead Output Interface Clock Output signal * RxOH_n: The Receive Overhead Output Interface Output signal.
The Receive Overhead Output Interface Clock Output pin (RxOHCLK_n) generates a rising clock edge for each data link bit position according to configuration of the framer. The data link bits extracted from the incoming T1 frames are outputted from the Receive Overhead Output Interface Output pin (RxOH_n) at the rising edge of RxOHClk_n. The Data Link equipment should sample and latch the data link bits at the falling edge of RxOHClk_n. The figure below shows block diagram of the Receive Overhead Output Interface of XRT86VL3x.
FIGURE 34. BLOCK DIAGRAM OF THE DS1 RECEIVE OVERHEAD OUTPUT INTERFACE OF XRT86VL3X
RxOH_n RxOHClk_n
Receive Overhead Output Interface
From Receive Framer Block
3.2.2
Configure the DS1 Receive Overhead Output Interface module as destination of the Facility Data Link (FDL) bits in ESF framing format mode
The FDL bits in ESF framing format mode can be extracted to:
* DS1 Receive Overhead Output Interface Block * DS1 Receive HDLC Controller * DS1 Receive Serial Output Interface.
The Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR) controls the extraction of FDL bits in ESF framing format mode. The table below shows configuration of the Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR).
33
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1-0
Receive Data Link Destination Select
R/W
00 - The extracted Facility Data Link bits are stored in either the LAPD controller or the SLC(R)96 buffer. At the same time, the extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 01 - The extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 10 - The extracted Facility Data Link bits are outputted from the framer through the Receive Overhead Output Interface via the RxOH_n pins. At the same time, the extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 11 - The Facility Data Link bits are forced to one by the framer.
If the Receive Data Link Source Select bits of the Receive Data Link Select Register are set to 10, the Receive Overhead Output Interface Block becomes Output source of the FDL bits. The XRT86VL3x allows the user to select bandwidth of the Facility Data Link Channel in ESF framing format mode. The FDL can be either a 4KHz or 2KHz data link channel. The Receive Data Link Bandwidth Select bits of the Receive Data Link Select Register (RDLSR) determine the bandwidth of FDL channel in ESF framing format mode. The table below shows configuration of the Receive Data Link Bandwidth Select bits of the Receive Data Link Select Register (TDLSR).
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
5-4
Receive Data Link Bandwidth Select
R/W
00 - The Facility Data Link is a 4KHz channel. All available FDL bits (first bit of every other frame) are used as data link bits. 01 - The Facility Data Link is a 2KHz channel. Only the odd FDL bits (first bit of frame 1, 5, 9...) are used as data link bits. 10 - The Facility Data Link is a 2KHz channel. Only the even FDL bits (first bit of frame 3, 7, 11...) are used as data link bits.
Figure 35 below shows the timing diagram of the Output and output signals associated with the DS1 Receive Overhead Output Interface module in ESF framing format mode.
34
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 35. DS1 RECEIVE OVERHEAD OUTPUT INTERFACE MODULE IN ESF FRAMING FORMAT MODE
1 2 3 4 5 6 7 8 9 1 0 1 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 9 2 0
REV. 1.2.0
Frame# RxSync RxOhClk (4KHz) RxOh (4KHz) RxOhClk (2KHz,odd) RxOh (2KHz,odd) RxOhClk (2KHz,even) RxOh (2KHz,even)
3.2.3
Configure the DS1 Receive Overhead Output Interface module as destination of the Signaling Framing (Fs) bits in N or SLC(R)96 framing format mode
The Fs bits in SLC(R)96 and N framing format mode can be extracted to:
* DS1 Receive Overhead Output Interface Block * DS1 Receive HDLC Controller * DS1 Receive Serial Output Interface.
The Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR) controls the destination of Fs bits in N or SLC(R)96 framing format mode. The table below shows configuration of the Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR).
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1-0
Receive Data Link Source Select
R/W
00 - The extracted Facility Data Link bits are stored in either the LAPD controller or the SLC(R)96 buffer. At the same time, the extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 01 - The extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 10 - The extracted Facility Data Link bits are outputted from the framer through the Receive Overhead Output Interface via the RxOH_n pins. At the same time, the extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 11 - The Facility Data Link bits are forced to one by the framer.
If the Receive Data Link Source Select bits of the Receive Data Link Select Register are set to 10, the Receive Overhead Output Interface Block outputs Fs bits extracted from the incoming T1 data stream.
35
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Figure 36 below shows the timing diagram of the output signals associated with the DS1 Receive Overhead Output Interface module in N or SLC(R)96 framing format mode. FIGURE 36. DS1 RECEIVE OVERHEAD OUTPUT INTERFACE TIMING IN N OR SLC(R)96 FRAMING FORMAT MODE
3.2.4
Configure the DS1 Receive Overhead Output Interface module as destination of the Remote Signaling (R) bits in T1DM framing format mode
The R bits in T1DM framing format mode can be extracted to:
* DS1 Receive Overhead Output Interface Block * DS1 Receive HDLC Controller * DS1 Receive Serial Output Interface.
The Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR) controls the destination of R bits in T1DM framing format mode. The table below shows configuration of the Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR).
RECEIVE DATA LINK SELECT REGISTER (RDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1-0
Receive Data Link Source Select
R/W
00 - The extracted Facility Data Link bits are stored in either the LAPD controller or the SLC(R)96 buffer. At the same time, the extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 01 - The extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 10 - The extracted Facility Data Link bits are outputted from the framer through the Receive Overhead Output Interface via the RxOH_n pins. At the same time, the extracted Facility Data Link bits are outputted from the framer through the Receive Serial Data Output Interface via the RxSer_n pins. 11 - The Facility Data Link bits are forced to one by the framer.
If the Receive Data Link Source Select bits of the Receive Data Link Select Register are set to 10, the Receive Overhead Output Interface Block outputs the R bits extracted from the incoming T1 data stream. Since R bit presents in Timeslot 24 of every T1DM frame, therefore, bandwidth of T1DM data link channel is 8KHz.
36
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
Figure 37 below shows the timing diagram of the output signals associated with the DS1 Receive Overhead Output Interface module in T1DM framing format mode. FIGURE 37. DS1 RECEIVE OVERHEAD OUTPUT INTERFACE TIMING IN T1DM FRAMING FORMAT MODE
3.3
E1 Overhead Interface Block
The XRT86VL3x has the ability to extract or insert E1 data link information from or into the E1 National bit sequence. The source and destination of these inserted and extracted data link bits would be from either the internal HDLC Controller or the external device accessible through E1 Overhead Interface Block. The operation of the Transmit Overhead Input Interface Block and the Receive Overhead Output Interface Block will be discussed separately.
3.4 3.4.1 E1 Transmit Overhead Input Interface Block Description of the E1 Transmit Overhead Input Interface Block
The E1 Transmit Overhead Input Interface Block will allow an external device to be the provider of the E1 National bit sequence. This interface provides interface signals and required interface timing to shift in proper data link information at proper time. The Transmit Overhead Input Interface for a given Framer consists of two signals.
* TxOHClk_n: The Transmit Overhead Input Interface Clock Output signal * TxOH_n: The Transmit Overhead Input Interface Input signal.
The Transmit Overhead Input Interface Clock Output pin (TxOHCLK_n) generates a rising clock edge for each National bit that is configured to carry Data Link information according to setting of the framer. The Data Link equipment interfaced to the Transmit Overhead Input Interface should update the data link bits on the TxOH_n line upon detection of the rising edge of TxOHClk_n. The Transmit Overhead Input Interface block will sample and latch the data link bits on the TxOH_n line on the falling edge of TxOHClk_n. The data link bits will be included in and transmitted via the outgoing E1 frames. The figure below shows block diagram of the DS1 Transmit Overhead Input Interface of XRT86VL3x.
37
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 38. BLOCK DIAGRAM OF THE E1 TRANSMIT OVERHEAD INPUT INTERFACE OF XRT86VL3X
TxOH_n TxOHClk_n
Transmit Overhead Input Interface
To Transmit Framer Block
3.4.2
Configure the E1 Transmit Overhead Input Interface module as source of the National Bit Sequence in E1 framing format mode
The National Bit Sequence in E1 framing format mode can be inserted from:
* E1 Transmit Overhead Input Interface Block * E1 Transmit HDLC Controller * E1 Transmit Serial Input Interface
The purpose of the Transmit Overhead Input Interface is to permit Data Link equipment direct access to the Sa4 through Sa8 National bits that are to be transported via the outbound frames. The Transmit Data Link Source Select [1:0] bits, within the Synchronization MUX Register (SMR) determine source of the Sa4 through Sa8 National bits to be inserted into the outgoing E1 frames. The table below shows configuration of the Transmit Data Link Source Select [1:0] bits of the Synchronization MUX Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (ADDRESS = 0XN109H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
3-2
Transmit Data Link Source Select [1:0]
R/W
00 - The Sa4 through Sa8 National bits are inserted into the framer through the Transmit Serial Data input Interface via the TxSer_n pins. 01 - The Sa4 through Sa8 National bits are inserted into the framer through the Transmit LAPD Controller. 10 - The Sa4 through Sa8 National bits are inserted into the framer through the Transmit Overhead Input Interface via the TxOH_n pins. 11 - The Sa4 through Sa8 National bits are inserted into the framer through the Transmit Serial Data input Interface via the TxSer_n pins.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Transmit Overhead Input Interface Block becomes input source of the FDL bits. The XRT86VL3x allows the user to decide on the following:
* How many of the National Bits will be used to carry the Data Link information bits * Which of these National Bits will be used to carry the Data Link information bits.
The Transmit Sa Data Link Select bits of the Transmit Signaling and Data Link Select Register (TSDLSR) determine which ones of the National bits are configured as Data Link bits in E1 framing format mode. Depending upon the configuration of the Transmit Signaling and Data Link Select Register, either of the following cases may exists:
* None of the National bits are used to transport the Data Link information bits (That is, data link channel of
XRT86VL3x is inactive).
38
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
* Any combination of between 1 and all 5 of the National bits can be selected to transport the Data Link
information bits. The table below shows configuration of the Transmit Sa Data Link Select bits of the Transmit Signaling and Data Link Select Register (TSDLSR).
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (ADDRESS = 0XN10AH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
7
Transmit Sa8 Data Link Select Transmit Sa7 Data Link Select Transmit Sa6 Data Link Select Transmit Sa5 Data Link Select Transmit Sa4 Data Link Select
R/W
0 - Source of the Sa8 Nation bit is not from the data link interface. 1 - Source the Sa8 National bit from the data link interface. 0 - Source of the Sa7 Nation bit is not from the data link interface. 1 - Source the Sa7 National bit from the data link interface. 0 - Source of the Sa6 Nation bit is not from the data link interface. 1 - Source the Sa6 National bit from the data link interface. 0 - Source of the Sa5 Nation bit is not from the data link interface. 1 - Source the Sa5 National bit from the data link interface. 0 - Source of the Sa4 Nation bit is not from the data link interface. 1 - Source the Sa4 National bit from the data link interface.
6
R/W
5
R/W
4
R/W
3
R/W
For every Sa bit that is selected to carry Data Link information, the Transmit Overhead Input Interface will supply a clock pulse, via the TxOHClk_n output pin, such that:
* The Data Link equipment interfaced to the Transmit Overhead Input Interface should update the data on the
TxOH_n line upon detection of the rising edge of TxOHClk_n.
* The Transmit Overhead Input Interface will sample and latch the data on the TxOH_n line on the falling edge
of TxOHClk_n.
39
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Figure 39 below shows the timing diagram of the input and output signals associated with the E1 Transmit Overhead Input Interface module in E1 framing format mode. FIGURE 39. E1 TRANSMIT OVERHEAD INPUT INTERFACE TIMING
40
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 3.5 3.5.1 E1 Receive Overhead Interface Description of the E1 Receive Overhead Output Interface Block
REV. 1.2.0
The E1 Receive Overhead Output Interface Block will allow an external device to be the consumer of the E1 National bit sequence. This interface provides interface signals and required interface timing to shift out proper data link information at proper time. The Receive Overhead Output Interface for a given Framer consists of two signals.
* RxOHClk_n: The Receive Overhead Output Interface Clock Output signal * RxOH_n: The Receive Overhead Output Interface Output signal.
The Receive Overhead Output Interface Clock Output pin (RxOHCLK_n) generates a rising clock edge for each National bit that is configured to carry Data Link information according to setting of the framer. The data link bits extracted from the incoming E1 frames are outputted from the Receive Overhead Output Interface Output pin (RxOH_n) before the rising edge of RxOHClk_n. The Data Link equipment should sample and latch the data link bits at the rising edge of RxOHClk_n. The figure below shows block diagram of the Receive Overhead Output Interface of XRT86VL3x.
FIGURE 40. BLOCK DIAGRAM OF THE E1 RECEIVE OVERHEAD OUTPUT INTERFACE OF XRT86VL3X
RxOH_n RxOHClk_n
Receive Overhead Output Interface
From Receive Framer Block
3.5.2
Configure the E1 Receive Overhead Output Interface module as source of the National Bit Sequence in E1 framing format mode
The National Bit Sequence in E1 framing format mode can be extracted and directed to:
* E1 Receive Overhead Output Interface Block * E1 Receive HDLC Controller * E1 Receive Serial Output Interface
The purpose of the Receive Overhead Output Interface is to permit Data Link equipment to have direct access to the Sa4 through Sa8 National bits that are extracted from the incoming E1 frames. Independent of the availability of the E1 Receive HDLC Controller module, the XRT86VL3x always output the received National bits through the Receive Overhead Output Interface block. The XRT86VL3x allows the user to decide on the following:
* How many of the National Bits is used to carry the Data Link information bits * Which of these National Bits is used to carry the Data Link information bits.
The Receive Sa Data Link Select bits of the Receive Signaling and Data Link Select Register (TSDLSR) determine which ones of the National bits are configured as Data Link bits in E1 framing format mode. Depending upon the configuration of the Receive Signaling and Data Link Select Register, either of the following cases may exists:
* None of the received National bits are used to transport the Data Link information bits (That is, data link
channel of XRT86VL3x is inactive).
* Any combination of between 1 and all 5 of the received National bits are used to transport the Data Link
information bits.
41
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The table below shows configuration of the Receive Sa Data Link Select bits of the Receive Signaling and Data Link Select Register (RSDLSR).
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (ADDRESS = 0XN10CH)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
7
Receive Sa8 Data Link Select Receive Sa7 Data Link Select Receive Sa6 Data Link Select Receive Sa5 Data Link Select Receive Sa4 Data Link Select
R/W
0 - The received Sa8 Nation bit is not extracted to the data link interface. 1 - The received Sa8 Nation bit is extracted to the data link interface. 0 - The received Sa7 Nation bit is not extracted to the data link interface. 1 - The received Sa7 Nation bit is extracted to the data link interface. 0 - The received Sa6 Nation bit is not extracted to the data link interface. 1 - The received Sa6 Nation bit is extracted to the data link interface. 0 - The received Sa5 Nation bit is not extracted to the data link interface. 1 - The received Sa5 Nation bit is extracted to the data link interface. 0 - The received Sa4 Nation bit is not extracted to the data link interface. 1 - The received Sa4 Nation bit is extracted to the data link interface.
6
R/W
5
R/W
4
R/W
3
R/W
For every received Sa bit that is determined to carry Data Link information, the Receive Overhead Output Interface will supply a clock pulse, via the RxOHClk_n output pin, such that:
* The Receive Overhead Output interface should update the data on the RxOH_n line before the rising edge of
RxOHClk_n.
* The external Data Link equipment interfaced to the Receive Overhead Output Interface will sample and latch
the data on the RxOH_n line on the rising edge of RxOHClk_n.
Figure 41 below shows the timing diagram of the output signals associated with the E1 Receive Overhead Output Interface module in E1 framing format mode. FIGURE 41. E1 RECEIVE OVERHEAD OUTPUT INTERFACE TIMING
42
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 4.0 LIU TRANSMIT PATH 4.1 Transmit Diagnostic Features
REV. 1.2.0
In addition to TAOS, the XRT86VL3x offers multiple diagnostic features for analyzing network integrity such as ATAOS, Network Loop Code generation, and QRSS on a per channel basis by programming the appropriate registers. These diagnostic features take priority over the digital data provided by the Framer block. The transmitters will send the diagnostic code to the line and will be maintained in the digital loopback if selected.
4.1.1 TAOS (Transmit All Ones)
The XRT86VL3x has the ability to transmit all ones on a per channel basis by programming the appropriate channel register. This function takes priority over the digital data provided by the Framer block. For example: If a fixed "0011" pattern is provided by the Framer block and TAOS is enabled, the transmitter will output all ones. Figure 42 is a diagram showing the all ones signal at TTIP and TRING.
FIGURE 42. TAOS (TRANSMIT ALL ONES)
1 TAOS 1 1
4.1.2
ATAOS (Automatic Transmit All Ones)
If ATAOS is selected by programming the appropriate global register, an AMI all ones signal will be transmitted for each channel that experiences an RLOS condition. If RLOS does not occur, the ATAOS will remain inactive until an RLOS on a given channel occurs. A simplified block diagram of the ATAOS function is shown in Figure 43.
FIGURE 43. SIMPLIFIED BLOCK DIAGRAM OF THE ATAOS FUNCTION
TTIP TRING TAOS
Tx
ATAOS RLOS
4.1.3
Network Loop Up Code
By setting the LIU to generate a NLUC, the transmitters will send out a repeating "00001" pattern. The output waveform is shown in Figure 44.
43
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 44. NETWORK LOOP UP CODE GENERATION
1 Network Loop-Up Code 0 0 0 0 1 0 0 0 0 1
4.1.4
Network Loop Down Code
By setting the LIU to generate a NLDC, the transmitters will send out a repeating "001" pattern. The output waveform is shown in Figure 45.
FIGURE 45. NETWORK LOOP DOWN CODE GENERATION
1 Network Loop-Down Code 0 0 1 0 0 1 0 0 1 0
4.1.5
QRSS Generation
The XRT86VL3x can transmit a QRSS random sequence to a remote location from TTIP/TRING. polynomial is shown in Table 3.
TABLE 3: RANDOM BIT SEQUENCE POLYNOMIALS
RANDOM PATTERN T1 E1
The
QRSS/PRBS
220 - 1
215 - 1
4.2
T1 Long Haul Line Build Out (LBO)
The long haul transmitter output pulses are generated using a 7-Bit internal DAC (6-Bits plus the MSB sign bit). The line build out can be set to -7.5dB, -15dB, or -22dB cable attenuation by programming the appropriate channel register. The long haul LBO consist of 32 discrete time segments extending over four consecutive periods of TCLK. As the LBO attenuation is increased, the pulse amplitude is reduced so that the waveform complies with ANSI T1.403 specifications. A long haul pulse with -7.5dB attenuation is shown in Figure 46, a pulse with -15dB attenuation is shown in Figure 47, and a pulse with -22.5dB attenuation is shown in Figure 48.
44
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 46. LONG HAUL LINE BUILD OUT WITH -7.5DB ATTENUATION
REV. 1.2.0
FIGURE 47. LONG HAUL LINE BUILD OUT WITH -15DB ATTENUATION
45
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 48. LONG HAUL LINE BUILD OUT WITH -22.5DB ATTENUATION
46
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 4.3 T1 Short Haul Line Build Out (LBO)
REV. 1.2.0
The short haul transmitter output pulses are generated using a 7-Bit internal DAC (6-Bit plus the MSB sign bit). The line build out can be set to interface to five different ranges of cable attenuation by programming the appropriate channel register. The pulse shape is divided into eight discrete time segments which are set to fixed values to comply with the pulse template. To program the eight segments individually to optimize a special line build out, see the arbitrary pulse section of this datasheet. The short haul LBO settings are shown in Table 4
TABLE 4: SHORT HAUL LINE BUILD OUT
LBO SETTING EQC[4:0] RANGE OF CABLE ATTENUATION
08h (01000) 09h (01001) 0Ah (01010) 0Bh (01011) 0Ch (01100)
0 - 133 Feet 133 - 266 Feet 266 - 399 Feet 399 - 533 Feet 533 - 655 Feet
4.3.1
Arbitrary Pulse Generator
The arbitrary pulse generator divides the pulse into eight individual segments. Each segment is set by a 7-Bit binary word by programming the appropriate channel register. This allows the system designer to set the overshoot, amplitude, and undershoot for a unique line build out. The MSB (bit 7) is a sign-bit. If the sign-bit is set to "0", the segment will move in a positive direction relative to a flat line (zero) condition. If this sign-bit is set to "1", the segment will move in a negative direction relative to a flat line condition. The resolution of the DAC is typically 60mV per LSB. Thus, writing 7-bit = 1111111 will clamp the output at either voltage rail corresponding to a maximum amplitude. A pulse with numbered segments is shown in Figure 49.
FIGURE 49. ARBITRARY PULSE SEGMENT ASSIGNMENT
1 2 3 Segment 1 2 3 4 5 6 7 8 Register 0x0Fn8 0x0Fn9 0x0Fna 0x0Fnb 0x0Fnc 0x0Fnd 0x0Fne 0x0Fnf 4
8 7 6 5
NOTE: By default, the arbitrary segments are programmed to 0x00h. The transmitter outputs will result in an all zero pattern to the line interface.
47
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION DMO (Digital Monitor Output)
4.3.2
The driver monitor circuit is used to detect transmit driver failures by monitoring the activities at TTIP/TRING outputs. Driver failure may be caused by a short circuit in the primary transformer or system problems at the transmit inputs. If the transmitter of a channel has no output for more than 128 clock cycles, DMO goes "High" until a valid transmit pulse is detected. If the DMO interrupt is enabled, the change in status of DMO will cause the interrupt pin to go "Low". Once the status register is read, the interrupt pin will return "High" and the status register will be reset (RUR).
4.3.3 Transmit Jitter Attenuator
The transmit path has a dedicated jitter attenuator to reduce phase and frequency jitter in the transmit clock. The jitter attenuator uses a data FIFO (First In First Out) with a programmable depth of 32-bit or 64-bit. When the Read and Write pointers of the FIFO are within 2-Bits of over-flowing or under-flowing, the bandwidth of the jitter attenuator is widened to track the short term input jitter, thereby avoiding data corruption. When this condition occurs, the jitter attenuator will not attenuate input jitter until the Read/Write pointer's position is outside the 2-Bit window. In T1 mode, the bandwidth of the JA is always set to 3Hz. In E1 mode, the bandwidth is programmable to either 10Hz or 1.5Hz (1.5Hz automatically selects the 64-Bit FIFO depth). The JA has a clock delay equal to 1/2 of the FIFO bit depth.
NOTE: The Receive Path has a dedicated jitter attenuator. See the Receive Path Line Interface Section.
4.4
Line Termination (TTIP/TRING)
The output stage of the transmit path generates standard return-to-zero (RZ) signals to the line interface for T1/ E1/J1 twisted pair or E1 coaxial cable. The physical interface is optimized by placing the terminating impedance inside the LIU. This allows one bill of materials for all modes of operation reducing the number of external components necessary in system design. The transmitter outputs only require one DC blocking capacitor of 0.68F. For redundancy applications (or simply to tri-state the transmitters), set TxTSEL to a "1" in the appropriate channel register. A typical transmit interface is shown in Figure 50.
FIGURE 50. TYPICAL CONNECTION DIAGRAM USING INTERNAL TERMINATION
XRT86VL3x LIU TTIP Transmitter Output C=0.68uF TRING Line Interface T1/E1/J1 1:2
One Bill of Materials Internal Impedance
48
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 5.0 LIU RECEIVE PATH 5.1 5.1.1 Line Termination (RTIP/RRING) Internal Termination
REV. 1.2.0
The input stage of the receive path accepts standard T1/E1/J1 twisted pair or E1 coaxial cable inputs through RTIP and RRING. The physical interface is optimized by placing the terminating impedance inside the LIU. This allows one bill of materials for all modes of operation reducing the number of external components necessary in system design. The receive termination impedance is selected by programming TERSEL[1:0] to match the line impedance. Selecting the internal impedance is shown in Table 5.
TABLE 5: SELECTING THE INTERNAL IMPEDANCE
TERSEL[1:0] RECEIVE TERMINATION
0h (00) 1h (01) 2h (10) 3h (11)
100 110 75 120
The XRT86VL3x has the ability to switch the internal termination to "High" impedance by programming RxTSEL in the appropriate channel register, if the RxTSEL hardware pin is "High". For internal termination, set RxTSEL to "1". By default, RxTSEL is set to "0" ("High" impedance). For redundancy applications, a dedicated hardware pin (RxTSEL) is available to control the receive termination for all channels simultaneously. This hardware pin is AND-ed with the register bit. Both, the register bit and the hardware pin must be set active for the receiver to be configured for internal impedance. Figure 51 shows a typical connection diagram using the internal termination.
FIGURE 51. TYPICAL CONNECTION DIAGRAM USING INTERNAL TERMINATION
XRT86VL3x LIU Receiver Input
RTIP
1:1 Line Interface T1/E1/J1
RRING 0.1F
One Bill of Materials
Internal Impedance
5.1.2
Equalizer Control
The main objective of the equalizer is to amplify an input attenuated signal to a pre-determined amplitude that is acceptable to the peak detector circuit. Using feedback from the peak detector, the equalizer will gain the input up to the maximum value specified by the equalizer control bits, in the appropriate channel register, normalizing the signal. Once the signal has reached the pre-determined amplitude, the signal is then processed within the peak detector and slicer circuit. A simplified block diagram of the equalizer and peak detector is shown in Figure 52.
49
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 52. SIMPLIFIED BLOCK DIAGRAM OF THE EQUALIZER AND PEAK DETECTOR
Peak Detector & Slicer
RTIP Rx Equalizer RRING
Rx Equalizer Control
5.1.3
Cable Loss Indicator
The ability to monitor the cable loss attenuation of the receiver inputs is a valuable feature. The XRT86VL3x contains a per channel, read only register for cable loss indication. CLOS[5:0] is a 6-Bit binary word that reports the value of cable loss in 1dB steps with an absolute accuracy of 1dB. An example of -25dB cable loss attenuation is shown in Figure 53.
FIGURE 53. SIMPLIFIED BLOCK DIAGRAM OF THE CABLE LOSS INDICATOR
-25dB Attenuated Signal -25dB of Cable Loss Equalizer and Peak Detector
XRT86VL3x
Read Only CLOS[5:0] = 0x19h (25dec = 19hex)
5.2
Receive Sensitivity
To meet Long Haul receive sensitivity requirements, the XRT86VL3x can accept T1/E1/J1 signals that have been attenuated by 43dB cable attenuation in E1 mode or 36dB cable attenuation in T1 mode without experiencing bit errors, LOF, pattern synchronization, etc. Short haul specifications are for 12dB of flat loss in E1 mode. T1 specifications are 655 feet of cable loss along with 6dB of flat loss in T1 mode. The XRT86VL3x can tolerate cable loss and flat loss beyond the industry specifications. The receive sensitivity in the short haul mode is approximately 4,000 feet without experiencing bit errors, LOF, pattern synchronization, etc. Although data integrity is maintained, the RLOS function (if enabled) will report an RLOS condition according to the receiver loss of signal section in this datasheet. The test configuration for measuring the receive sensitivity is shown in Figure .
50
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 54. TEST CONFIGURATION FOR MEASURING RECEIVE SENSITIVITY
W&G ANT20 Tx Cable Loss Network Analyzer Rx Rx Flat Loss Tx XRT86VL3x N-Channel Framer/LIU External Loopback
REV. 1.2.0
E1 = PRBS 215 - 1 T1 = PRBS 223 - 1
5.2.1
AIS (Alarm Indication Signal)
The XRT86VL3x adheres to the ITU-T G.775 specification for an all ones pattern. The alarm indication signal is set to "1" if an all ones pattern (at least 99.9% ones density) is present for T, where T is 3ms to 75ms in T1 mode. AIS will clear when the ones density is not met within the same time period T. In E1 mode, the AIS is set to "1" if the incoming signal has 2 or less zeros in a 512-bit window. AIS will clear when the incoming signal has 3 or more zeros in the 512-bit window.
5.2.2 NLCD (Network Loop Code Detection)
The Network Loop Code Detection can be programmed to detect a Loop-Up, Loop-Down, or Automatic Loop Code. If the network loop code detection is programmed for Loop-Up, the NLCD will be set "High" if a repeating pattern of "00001" occurs for more than 5 seconds. If the network loop code detection is programmed for Loop-Down, the NLCD will be set "High" if a repeating pattern of "001" occurs for more than 5 seconds. If the network loop code detection is programmed for automatic loop code, the LIU is configured to detect a Loop-Up code. If a Loop-Up code is detected for more than 5 seconds, the XRT86VL3x will automatically program the channel into a remote loopback mode. The LIU will remain in remote loopback even if the Loop-Up code disappears. The channel will continue in remote loop back until a Loop-Down code is detected for more than 5 seconds (or, if the automatic loop code is disabled) and then automatically return to normal operation with no loop back. The process of the automatic loop code detection is shown in Figure 55.
51
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 55. PROCESS BLOCK FOR AUTOMATIC LOOP CODE DETECTION
No
Loop-Up Code for 5 sec?
Yes
Automatic Remote Loopback
No
Loop-Down Code for 5 sec?
Yes
Disable Remote Loopback
5.2.3
FLSD (FIFO Limit Status Detection)
The purpose of the FIFO limit status is to indicate when the Read and Write FIFO pointers are within a predetermined range (over-flow or under-flow indication). The FLSD is set to "1" if the FIFO Read and Write Pointers are within 3-Bits.
5.2.4 Receive Jitter Attenuator
The receive path has a dedicated jitter attenuator to reduce phase and frequency jitter in the recovered clock. The jitter attenuator uses a data FIFO (First In First Out) with a programmable depth of 32-bit or 64-bit. If the LIU is used for line synchronization (loop timing systems), the JA should be enabled in the receive path. When the Read and Write pointers of the FIFO are within 2-Bits of over-flowing or under-flowing, the bandwidth of the jitter attenuator is widened to track the short term input jitter, thereby avoiding data corruption. When this condition occurs, the jitter attenuator will not attenuate input jitter until the Read/Write pointer's position is outside the 2-Bit window. In T1 mode, the bandwidth of the JA is always set to 3Hz. In E1 mode, the bandwidth is programmable to either 10Hz or 1.5Hz (1.5Hz automatically selects the 64-Bit FIFO depth). The JA has a clock delay equal to 1/2 of the FIFO bit depth.
NOTE: The Transmit Path has a dedicated jitter attenuator. See the Transmit Path Line Interface Section.
5.2.5
RxMUTE (Receiver LOS with Data Muting)
The receive muting function can be selected by setting RxMUTE to "1" in the appropriate global register. If selected, any channel that experiences an RLOS condition will automatically pull the output of the LIU section "Low" to prevent data chattering. If RLOS does not occur, the RxMUTE will remain inactive until an RLOS on a given channel occurs. The default setting for RxMUTE is "0" which is disabled. A simplified block diagram of the RxMUTE function is shown in Figure 56.
52
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 56. SIMPLIFIED BLOCK DIAGRAM OF THE RXMUTE FUNCTION
REV. 1.2.0
LIU
Digital Output
Framer
RxMUTE RLOS
53
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
6.0 THE E1 TRANSMIT/RECEIVE FRAMER 6.1 Description of the Transmit/Receive Payload Data Input Interface Block
Each framer within the XRT86VL3x device includes a Transmit and Receive Payload Data Input Interface block. Although most configurations are independent for the Tx and Rx path, once E1 framing has been selected, both the Tx and Rx must operate in E1. The Payload Data Input Interface module (also known as the Back-plane Interface module) supports payload data to be taken from or presented to the system. In E1 mode, supported data rates are 2.048Mbit/s, MVIP 2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s, or H.100 16.384Mbit/s.
6.1.1 Brief Discussion of the Transmit/Receive Payload Data Input Interface Block Operating at XRT84V24 Compatible 2.048Mbit/s mode
Whether or not the transmit/receive interface signals have been chosen as inputs or outputs, the overall system timing diagrams remain the same. It is the responsibility of the Terminal Equipment to provide serial input data through the TxSER pin aligned with the Transmit Single-frame Synchronization signal and the Transmit Multi-frame Synchronization signal. Figure 57 shows how to connect the Transmit Payload Data Input Interface block to local Terminal Equipment. Figure 58 shows how to connect the Receive Payload Data Output Interface to local Terminal Equipment.
FIGURE 57. INTERFACING THE TRANSMIT PATH TO LOCAL TERMINAL EQUIPMENT
XRT86VL3x TxSERCLK0 TxSER0 TxMSYNC0 TxSYNC0 TxCHCLK0 TxCHN[4:0]_0 Terminal Equipment Transmit Payload Data Input Interface Chn 0
TxSERCLKn TxSERn TxMSYNCn TxSYNCn TxCHCLKn TxCHN[4:0]_n Transmit Payload Data Input Interface Chn N
54
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 58. INTERFACING THE RECEIVE PATH TO LOCAL TERMINAL EQUIPMENT
XRT86VL38 RxSERCLK0 RxSER0 RxMSYNC0 RxSYNC0 RxCHCLK0 RxCHN[4:0]_0 Terminal Equipment Receive Payload Data Input Interface Chn 0
REV. 1.2.0
RxSERCLK7 RxSER7 RxMSYNC7 RxSYNC7 RxCHCLK7 RxCHN[4:0]_7 Receive Payload Data Input Interface Chn 7
Figure 59 shows the waveforms for connecting the Transmit Payload Data Input Interface block to local Terminal Equipment. Figure 60 shows the waveforms for connecting the Receive Payload Data Input Interface block to local Terminal Equipment. FIGURE 59. WAVEFORMS FOR CONNECTING THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK TO LOCAL TERMINAL EQUIPMENT
Timeslot 1 TxSERCLK TxSERCLK (INV) TxSER TxSYNC(input) If Tx Fractional E1 Input Enable = 0 TxCHCLK TxCHN[4:0] Timeslot #1 Timeslot #15 Timeslot #16 Timeslot #32 Input Data Input Data Signaling Input Data Timeslot 15 Timeslot 16 Timeslot 32
If Tx Fractional E1 Input Enable = 1 TxCHN[0]/TxSIG TxCHN[2]/TxTS TxCHCLK TxCHN[1]/TxFrTD 12345678 12345678 ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
55
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 60. WAVEFORMS FOR CONNECTING THE RECEIVE PAYLOAD DATA INPUT INTERFACE BLOCK TO LOCAL TERMINAL EQUIPMENT
Timeslot 0 RxSerClk RxSer Rx Fractional Enable Bit = 0 RxSync(output) RxCHClk RxCHN[4:0] Timeslot #0 Timeslot #5 Timeslot #6 Timeslot #31 Input Data Input Data Timeslot 5 Timeslot 6 Timeslot 31
Rx Fractional Enable Bit = 1 RxCHN[0]/RxSig RxCHN[2]/RxChn RxCHClk RxCHN[1]/RxFrTD 12345678 ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
6.2
Transmit/Receive High-Speed Back-Plane Interface
The High-speed Back-plane Interface supports payload data to be taken from or presented to the Terminal Equipment at different data rates. In the non-multiplexed mode, payload data of each channel are interfaced to the Terminal Equipment separately. Each channel uses its own serial clock, serial data, single-frame synchronization signal and multi-frame synchronization signals.
6.2.1 Non-Multiplexed High-Speed Mode
When the Back-plane interface data rate is MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s, the interface signals are all configured as inputs, except the receive serial data on RxSER and the multi frame sync pulse provided by the framer. The Transmit Serial Clock for each channel is always an input clock with frequency of 2.048 MHz for all data rates so that it may be used as the timing reference for the transmit line rate. The TxMSYNC signal is configured as the Transmit Input Clock with frequencies of 2.048 MHz, 4.096 MHz and 8.192 MHz respectively. It serves as the primary clock source for the High-speed Back-plane Interface. Figure 61 shows how to connect the Transmit non-multiplexed high-speed Input Interface block to local Terminal Equipment. Figure 62 shows how to connect the Receive non-multiplexed high-speed Output Interface to local Terminal Equipment.
56
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 61. TRANSMIT NON-MULTIPLEXED HIGH-SPEED CONNECTION TO LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S, 4.096MBIT/S, OR 8.192MBIT/S
TxINCLK = 2.048/4.096/8.192MHz TxSERCLK0 TxSER0 TxINCLK0 TxSYNC0 Terminal Equipment TxSERCLK7 TxSER7 TxINCLK7 TxSYNC7
XRT86VL38
Transmit Payload Data Input Interface Chn 0
Transmit Payload Data Input Interface Chn 7
FIGURE 62. RECEIVE NON-MULTIPLEXED HIGH-SPEED CONNECTION TO LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S, 4.096MBIT/S, OR 8.192MBIT/S
RxSERCLK = 2.048/4.096/8.192MHz XRT86VL38 RxSERCLK0 RxSER0 RxMSYNC0 RxSYNC0 Terminal Equipment RxSERCLK7 RxSER7 RxMSYNC7 RxSYNC7 Receive Payload Data Input Interface Chn 7 Receive Payload Data Input Interface Chn 0
57
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Figure 63 shows the waveforms for connecting the Transmit non-multiplexed high-speed Input Interface block to local Terminal Equipment. Figure 64 shows the waveforms for connecting the Receive non-multiplexed high-speed Input Interface block to local Terminal Equipment. FIGURE 63. WAVEFORMS FOR CONNECTING THE TRANSMIT NON-MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT MVIP 2.048MBIT/S, 4.096MBIT/S, AND 8.192MBIT/S
TxMsync (2/4/8MHz) TxSERCLK TxSERCLK (INV) TxSER TxSync(input) TxSync(input) MVIP mode TxCHN[0]/TxSig TxSyncFrd=0 TxCHCLK TxCHN[1]/TxFrTD TxSyncFrd=1 TxCHN[1]/TxFrTD TxCHCLK Don't Care 12345678 Don't Care 12345678 Don't Care 12345678 Don't Care 12345678 Don't Care A B C D Don't Care A B C D Don't Care A B C D Don't Care A B C D Don't Care A B C D 12345678123456781234567 812345678 1234567812345678
FIGURE 64. WAVEFORMS FOR CONNECTING THE RECEIVE NON-MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT MVIP 2.048MBIT/S, 4.096MBIT/S, AND 8.192MBIT/S
Timeslot 0 RxSERCLK (2/4/8MHz) RxSERCLK RxSERCLK (INV) RxSER RxSync(input) RxSync(input) MVIP mode RxCHN[0]/RxSig Don't Care A B C D Don't Care A B C D Don't Care A B C D Don't Care A B C D Don't Care A B C D 12345678123456781234567812345678 1234567812345678 Timeslot 1 Timeslot 2 Timeslot 3 Timeslot 4 Timeslot 5
RxSyncFrd=0
RxCHCLK RxCHN[1]/RxFrTD Don't Care 12345678 Don't Care 12345678
RxSyncFrd=1
RxCHN[1]/RxFrTD RxCHCLK Don't Care 12345678 Don't Care 12345678
58
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 6.2.2 Multiplexed High-Speed Mode
REV. 1.2.0
Bit-Multiplexed 16.384Mbit/s When the Back-plane interface data rate is 16.384Mbit/s, HMVIP 16.384Mbit/s, and H.100 16.384Mbit/s, the interface signals are all configured as inputs, except the receive serial data on RxSER and the multi frame sync pulse provided by the framer. The Transmit Serial Clock for each channel is always an input clock with frequency of 2.048 MHz for all data rates so that it may be used as the timing reference for the transmit line rate. The TxMSYNC signal is configured as the Transmit Input Clock with frequency of 16.384 MHz. It serves as the primary clock source for the High-speed Back-plane Interface. Payload and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4. The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH at the beginning of the multiplexed frame with data from Channel 0-3 multiplexed together. The Transmit Single-frame Synchronization signal of Channel 4 pulses HIGH at the beginning of the multiplexed frame with data from Channel 4-7 multiplexed together. It is the responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchronization pulse. Additionally, each channel requires the local Terminal Equipment to provide a freerunning 2.048 MHz clock into the Transmit Serial Clock input. The local Terminal Equipment maps four 2.048Mbit/s E1 data streams into one 16.384Mbit/s serial data stream as described below: 1. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2. The first payload bit of Timeslot 0 of Channel 3 is sent last. After the first bit of Timeslot 0 of all four channels are sent, it comes the second bit of Timeslot 0 of Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into the 16.384Mbit/s data stream.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y 2. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384Mbit/s data stream. When the Terminal Equipment is sending the fifth payload bit of one channel, instead of sending it twice, it inserts the signaling bit A of that corresponding channel. Similarly, the sixth payload bit is followed by the signaling bit B of that corresponding channel; the seventh payload bit is followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D. The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/s data stream.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
59
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y AY: The signaling bit A of Channel Y 3. After the first octet of all four channels are sent, the local Terminal Equipment start sending the second octets following the same rules of Step 1 and 2. The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit position of the multiplexed data stream with data from Channel 0-3 multiplexed together. The Transmit Singleframe Synchronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position of the data stream with data from Channel 4-7 multiplexed together. By sampling the HIGH pulse on the Transmit Singleframe Synchronization signal, the framer can position the beginning of the multiplexed E1 frame. It is the responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit Singleframe Synchronization pulse. Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are de-multiplexed inside the XRT86VL3x device and send to each individual channel. These data will be processed by each individual framer and send to LIU interface. The local Terminal Equipment provides a freerunning 2.048MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. Figure 65 shows how to connect the Transmit multiplexed high-speed Input Interface block to local Terminal Equipment. Figure shows the timing signals when framer is running at 16.384MHz Bit-Multiplexed mode.
HMVIP/ H100 16.384Mbit/s Byte-Multiplexed Mode
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to 10, the Transmit Back-plane interface of framer is running at HMVIP 16.384MHz. When Transmit Interface Mode Select[1:0] bits are set to 11, the Transmit Back-plane interface is running at H100 16.384MHz mode. The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 16.384Mbit/s. The local Terminal Equipment multiplexes payload data of every four channels into one data stream. Payload data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Payload data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4. Free-running clocks of 16.384MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of the framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit Input Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at falling edge of the clock.
60
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
The local Terminal Equipment maps four 2.048Mbit/s E1 data streams into this 16.384Mbit/s data stream as described below: 1. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first payload bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel 0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel 3 are sent last. After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload bits of Timeslot 1 of Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into one 16.384Mbit/s data stream
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y 2. When the framer is running at HMVIP or H100 16.384MBit/s byte-mulitplexed mode, signaling information is inserted from the TxSig/TSb[0] pin or from the TSCR register (0xn340-n35F). When the local terminal is sending the fifth payload bit of one channel, signaling bit A of that corresponding channel is repeated and sent through the TxSig/TSb[0] pin; Similarly, signaling bit B, C, and D of the corresponding channel is repeated and sent through the TxSig/TSb[0] pin when the local terminal is providing the sixth, seventh, and eighth payload bit respectively, as shown in Figure 67. 3. After the first octet of all four channels are sent, the local Terminal Equipment start sending the second octets following the same rules of Step 1 and 2. For HMVIP mode, the Transmit Single-frame Synchronization signal should pulse HIGH for four clock cycles (the last two bit positions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. For H100 mode, the Transmit Single-frame Synchronization signal should pulse HIGH for two clock cycles (the last bit position of the previous multiplexed frame and the first bit position of the next multiplexed frame). The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH to identify the start of multiplexed data stream of Channel 0-3. The Transmit Single-frame Synchronization signal of Channel 4 pulses HIGH to identify the start of multiplexed data stream of Channel 4-7. By sampling the HIGH pulse on the Transmit Single-frame Synchronization signal, the framer
61
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
can position the beginning of the multiplexed E1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchronization pulse. Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are de-multiplexed inside the XRT86VL3x device and send to each individual channel. These data will be processed by each individual framer and send to LIU interface. The local Terminal Equipment provides a freerunning 2.048MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. See Figure 65 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Interface block of the framer in HMVIP or H100 16.384Mbit/s mode. Figure 67 shows the timing signals when the framer is running at HMVIP or H100 16.384 MHz mode. FIGURE 65. INTERFACING XRT86VL3X TRANSMIT TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S, HMVIP 16.384MBIT/S, AND H.100 16.384MBIT/S
XRT86VL38 TxSER0 TxINCLK0 (16.384MHz) TxSYNC0 TxSERCLK0 (2.048MHz) TxSERCLK1 (2.048MHz) TxSERCLK2 (2.048MHz) TxSERCLK3 (2.048MHz) Terminal Equipment
Transmit Payload Data Input Interface Chn 0
Chn 1 Chn 2 Chn 3
TxSER4 TxINCLK4 (16.384MHz) TxSYNC4 TxSERCLK4 (2.048MHz) TxSERCLK5 (2.048MHz) TxSERCLK6 (2.048MHz) TxSERCLK7 (2.048MHz)
Transmit Payload Data Input Interface Chn 4
Chn 5 Chn 6 Chn 7
FIGURE 66. TIMING SIGNAL WHEN THE FRAMER IS RUNNING AT BIT-MULTIPLEXED 16.384MBIT/S MODE
TxInClk (16.384MHz) TxInClk (INV) TxSer TxSync(input) h0 X h1 X h 2 X h3 X 56 cycles
8-bit header
1 0 X 11 X 12 X 1 3 X 20 X 21 X
30 X
40 X
50 A0 51 A1 52 A2 53 A3
62
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 67. WAVEFORMS FOR CONNECTING THE TRANSMIT MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT HMVIP AND H.100 16.384MBIT/S MODE
TxInClk (16.384MHz) TxInClk (INV)
TxSer
73 73 83 83 h0 h0 h0 h0 h0 h0 h0 h0 Start of Frame C3C3 D3 D3 1 1 1 1 1 1 1 1
56 cycles 56 cycles
TxSig TxSync(input) HMVIP, negative sync TxSync(input) HMVIP, positive sync TxSync(input) H.100, negative sync TxSync(input) H.100, positive sync Delayer H.100 TxSync(input) H.100, negative sync TxSync(input) H.100, positive sync
10 10 20 20 30 30 40 40 50 50 60 60 12 12 52 52 53 53 63 63 73 73 83 83 Xy : X is the bit number and y is the channel number 0 0 0 0 0 0 0 0 A0 A0 B0 B0 00 A2 A2 A3 A3 B3 B3 C3 C3D3 D3
E1 Receive Multiplexed Mode
The interface consists of the following pins:
* Data Output (RxSer_n) * Receive Serial Clock Input signal (RxSerClk_n) * Receive Single-frame Synchronization Input signal (RxSync_n)
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 16.384Mbit/s. It multiplexes payload and signaling data of every four channels into one data stream. Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of Channel 4. Free-running clocks of 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Receive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock. Figure 68 shows the interface of the Recieve Payload Data Output Interface Block to the Terminal Equipment. The multiplexed data output on RxSER_0 or RxSER_4 are very similar to the Multiplexed data input on TxSER_0 or TxSER_4 except when the receive framer is running at 16MHz Bit-Multiplexed mode. When the receive framer is running at 16MHz Bit-Multiplexed mode, the multiplexed data on RxSER_0 or RxSER_4 are return-to-zero data when the receive framer is processing the first four bits of each time slot data of each channel, as shown in Figure . Figure shows the timing signal when the receive framer is running at HMVIP or H.100 16.384 MHz mode.
63
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 68. INTERFACING XRT86VL3X RECEIVE TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S, HMVIP 16.384MBIT/S, AND H.100 16.384MBIT/S
XRT86VL38 RxSER0 Transmit RxSERCLK0 (12/16MHz) Payload Data Input RxSYNC0 Interface Chn 0 Chn 1 Chn 2 Chn 3 Terminal Equipment RxSER4 RxSERCLK (12/16MHz) RxSYNC4 Transmit Payload Data Input Interface Chn 4 Chn 5 Chn 6 Chn 7
FIGURE 69. TIMING SIGNAL WHEN THE RECEIVE FRAMER IS RUNNING AT 16.384MHZ BIT-MULITPLEXED MODE
RxSerClk (16.384MHz) RxSerClk (INV) RxSer RxSync(input) h0 X h1 X h2 X h3 X 56 cycles
8-bit header
10 0 11 0 12 0 13 0 20 0 21 0
30 0
40 0
50 A0 51 A1 52 A2 53 A3
FIGURE 70. TIMING SIGNAL WEHN THE RECEIVE FRAMER IS RUNNING AT HMVIP AND H100 16.384MHZ MODE
RxSerClk (16.384MHz) RxSerClk (INV)
RxSer
7 3 73 83 83 h0 h0 h1 h 1 h2 h 2 h3 h 3 Start of Frame C3 C3D3 D3 1 1 1 1 1 1 1 1
56 cycles 56 cycles
10 10 20 20 30 30 40 4 0 50 5 0 60 6 0 12 12 52 52 5 3 53 6 3 63 7 3 73 83 83 Xy : X is the bit number and y is the channel number 0 0 0 0 0 0 0 0 A0 A0 B0 B0 00 A2 A2 A3 A3 B3 B3 C3 C3D3 D3
RxSig
RxSync(input) H.100, negative sync RxSync(input) H.100, positive sync
RxSync(input) HMVIP, negative sync RxSync(input) HMVIP, positive sync
64
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
6.3 Brief Discussion of Common Channel Signaling in E1 Framing Format
REV. 1.2.0
As the name referred, Common Channel Signaling is signaling information common to all thirty voice or data channels of an E1 trunk. Time slot 16 may be used to carry Common Channel Signaling data of up to a rate of 64kbits/s. The national bits of time slot 0 may also be used for Common Channel Signaling. Since there are five national bits of time slot 0 per every two E1 frames, the total bandwidth of the national bits is 20kbits/s. The Common Channel Signaling is essentially data link information that provides performance monitoring and a transmission quality report.
6.4 Brief Discussion of Channel Associated Signaling in E1 Framing Format
Signaling is required when dealing with voice and dial-up data services in E1 applications. Traditionally, signaling is provided on a dial-up telephone line across the talk-path. Signaling is used to tell the receiver where the call or route is destined. The signal is sent through switches along the route to a distant end. Common types of signals are:
* On hook * Off hook * Dial tone * Dialed digits * Ringing cycle * Busy tone
A signal is consists of four bits namely A, B, C and D. These bits define the state of the call for a particular time slot. Time slot 16 of each E1 frame can carry CAS signals for two E1 voice or data channels. Therefore, sixteen E1 frames are needed to carry CAS signals for all 32 E1 channels. The sixteen E1 frames then forms a CAS Multi-frame.
6.5 Insert/Extract Signaling Bits from TSCR Register
The four most significant bits of the Transmit Signaling Control Register (TSCR) of each time slot can be used to store outgoing signaling data. The user can program these bits through microprocessor access. If the XRT86VL3x framer is configure to insert signaling bits from TSCR registers, the E1 Transmit Framer block will fill up the time slot 16 octet with the signaling bits stored inside the TSCR registers. The insertion of signaling bit into PCM data is done on a per-channel basis. The most significant bit (Bit 7) of TSCR register is used to store Signaling bit A. Bit 6 is used to hold Signaling bit B. Bit 5 is used to hold Signaling bit C. Bit 4 is used to hold Signaling bit D.
6.6 Insert/Extract Signaling Bits from TxCHN[0]_n/TxSIG Pin
The XRT86VL3x framer can be configured to insert/extract signaling bits provided by external equipment through the external signaling bus. When the Fractional E1 mode is enabled, this bus is configured as TxSIG and RxSIG. These pins act as an the signaling bus for the outbound E1 frames. Figure 71 shows a timing diagram of the TxSIG input pin. Figure 72 shows a timing diagram of the RxSIG output pin. Please note that the Signaling Bit A of a certain channel coincides with Bit 5 of the PCM data of that channel; Signaling Bit B coincides with Bit 6 of the PCM data; Signaling Bit C coincides with Bit 7 of the PCM data and Signaling Bit D coincides with Bit 8 (LSB) of the PCM data.
65
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 71. TIMING DIAGRAM OF THE TXSIG INPUT
FIGURE 72. TIMING DIAGRAM OF THE RXSIG OUTPUT
6.7
Enable Channel Associated Signaling and Signaling Data Source Control
The Transmit Signaling Control Register (TSCR) of each channel selects source of signaling data to be inserted into the outgoing E1 frame and enables Channel Associated signaling. As we mentioned before, the signaling data can be inserted from Transmit Signaling Control Registers (TSCR) of each timeslot, from the TxSig_n input pin, from the TxOH_n input pin or from the TxSer_n input pin. The Transmit Signaling Data Source Select [1:0] bits of the Transmit Signaling Control Register (TSCR) determines from which sources the signaling data is inserted from.
66
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 7.0 THE DS1 TRANSMIT/RECEIVE FRAMER
7.1 Description of the Transmit/Receive Payload Data Input Interface Block
REV. 1.2.0
Each of the four framers within the XRT86VL3x device includes a Transmit and Receive Payload Data Input Interface block. Although most configurations are independent for the Tx and Rx path, once T1 framing has been selected, both the Tx and Rx must operate in T1. The Payload Data Input Interface module (also known as the Back-plane Interface module) supports payload data to be taken from or presented to the system. In T1 modes, supported data rates are 1.544Mbit/s, MVIP 2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 12.352Mbit/s, 16.384Mbit/s, HMVIP 16.384Mbit/s, or H.100 16.384Mbit/s. 7.1.1 Brief Discussion of the Transmit/Receive Payload Data Input Interface Block Operating at 1.544Mbit/s mode
Whether or not the transmit/receive interface signals have been chosen as inputs or outputs, the overall system timing diagrams remain the same. It is the responsibility of the Terminal Equipment to provide serial input data through the TxSER pin aligned with the Transmit Single-frame Synchronization signal and the Transmit Multi-frame Synchronization signal. Figure 73 shows how to connect the Transmit Payload Data Input Interface block to local Terminal Equipment. Figure 74 shows how to connect the Receive Payload Data Output Interface to local Terminal Equipment. FIGURE 73. INTERFACING THE TRANSMIT PATH TO LOCAL TERMINAL EQUIPMENT
XRT86VL3x TxSERCLK0 TxSER0 TxMSYNC0 TxSYNC0 TxCHCLK0 TxCHN[4:0]_0 Terminal Equipment Transmit Payload Data Input Interface Chn 0
TxSERCLKn TxSERn TxMSYNCn TxSYNCn TxCHCLKn TxCHN[4:0]_n Transmit Payload Data Input Interface Chn N
67
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 74. INTERFACING THE RECEIVE PATH TO LOCAL TERMINAL EQUIPMENT
XRT86VL3x RxSERCLK0 RxSER0 RxMSYNC0 RxSYNC0 RxCHCLK0 RxCHN[4:0]_0 Terminal Equipment Receive Payload Data Input Interface Chn 0
RxSERCLKn RxSERn RxMSYNCn RxSYNCn RxCHCLKn RxCHN[4:0]_n Receive Payload Data Input Interface Chn N
Figure 75 shows the waveforms for connecting the Transmit Payload Data Input Interface block to local Terminal Equipment. Figure 76 shows the waveforms for connecting the Receive Payload Data Input Interface block to local Terminal Equipment. FIGURE 75. WAVEFORMS FOR CONNECTING THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK TO LOCAL TERMINAL EQUIPMENT
TxSerClk (1.544MHz) TxSerClk (INV) TxSer TxSync(input) If Tx Fractional Input Enbale = 0 TxCHClk TxCHN[4:0] Timeslot #0 Timeslot #5 Timeslot #6 Timeslot #23 F Input Data Input Data Input Data Input Data F Timeslot 0 Timeslot 5 Timeslot 6 Timeslot 23
If Tx Fractional Input Enbale = 1 TxCHN[0]/TxSig TxCHN[2]/TxCHN TxCHCLK TxCHN[1]/TxFrTD 12345678 12345678 ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
68
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 76. WAVEFORMS FOR CONNECTING THE RECEIVE PAYLOAD DATA INPUT INTERFACE BLOCK TO LOCAL TERMINAL EQUIPMENT
Timeslot 0 RxSerClk RxSer RxSync(output) Rx Fractional Enable Bit = 0 RxCHClk RxCHN[4:0] Timeslot #0 Timeslot #5 Timeslot #6 Timeslot #23 F Input Data Input Data Timeslot 5 Timeslot 6 Timeslot 23
Rx Fractional Enable Bit = 1 RxCHN[0]/RxSig RxCHN[2]/RxCHN RxCHClk RxCHN[1]/RxFrTD 12345678 ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
ABCD
c1 c2 c3 c4 c5
7.2
Transmit/Receive High-Speed Back-Plane Interface
The High-speed Back-plane Interface supports payload data to be taken from or presented to the Terminal Equipment at different data rates. In the non-multiplexed mode, payload data of each channel are interfaced to the Terminal Equipment separately. Each channel uses its own serial clock, serial data, single-frame synchronization signal and multi-frame synchronization signals. 7.2.1 T1 Transmit/Receive Interface - MVIP 2.048 MHz
The Back-plane interface is processing data at an E1 equivalent data rate of 2.048Mbit/s. The local Terminal Equipment should pump in data grouped in 256-bit frame 8000 times every second. Each frame consists of thirty-two octets as in E1. The local Terminal Equipment maps a 193-bit T1 frame into this 256-bit format as described below: 1. The Framing (F-bit) is mapped into MSB of the first E1 Time-slot. The local Terminal Equipment will stuff the other seven bits of the first octet with don't care bits that would be ignored by the framer. 2. Payload data of T1 Time-slot 0, 1 and 2 are mapped into E1 Time-slot 1, 2 and 3. 3. The local Terminal Equipment will stuff E1 Time-slot 4 with eight don't care bits that would be ignored by the framer. 4. Following the same rules of Step 2 and 3, the local Terminal Equipment maps every three time-slots of T1 payload data into four E1 time-slots.
69
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The mapping of T1 frame into E1 framing format is shown in the table below. TABLE 6: MAPPING A T1 FRAME INTO AN E1 FRANE
T1 E1 T1 E1 T1 E1 T1 E1 F-Bit TS0 Don't Care Bits TS8 Don't Care Bits TS16 Don't Care Bits TS24 TS0 TS1 TS6 TS9 TS12 TS17 TS18 TS25 TS1 TS2 TS7 TS10 TS13 TS18 TS19 TS26 TS2 TS3 TS8 TS11 TS14 TS19 TS20 TS27 Don't Care Bits TS4 Don't Care Bits TS12 Don't Care Bits TS20 Don't Care Bits TS28 TS3 TS5 TS9 TS13 TS15 TS21 TS21 TS29 TS4 TS6 TS10 TS14 TS16 TS22 TS22 TS30 TS5 TS7 TS11 TS15 TS17 TS23 TS23 TS31
7.2.2
Non-Multiplexed High-Speed Mode
When the Back-plane interface data rate is MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s, the interface signals are all configured as inputs, except the receive serial data on RxSER and the multi frame sync pulse (RxMSYNC) provided by the framer. The Transmit Serial Clock for each channel is always an input clock with frequency of 1.544 MHz for all data rates so that it may be used as the timing reference for the transmit line rate. The TxMSYNC signal is configured as the Transmit Input Clock with frequencies of 2.048 MHz, 4.096 MHz and 8.192 MHz respectively. It serves as the primary clock source for the High-speed Back-plane Interface. Figure 77 shows how to connect the Transmit non-multiplexed high-speed Input Interface block to local Terminal Equipment. Figure 78 shows how to connect the Receive non-multiplexed high-speed Output Interface to local Terminal Equipment. FIGURE 77. TRANSMIT NON-MULTIPLEXED HIGH-SPEED CONNECTION TO LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S, 4.096MBIT/S, OR 8.192MBIT/S
TxINCLK = 2.048/4.096/8.192MHz XRT86VL3x TxSERCLK0 TxSER0 TxINCLK0 TxSYNC0 Terminal Equipment TxSERCLKn TxSERn TxINCLKn TxSYNCn Transmit Payload Data Input Interface Chn N Transmit Payload Data Input Interface Chn 0
70
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 78. RECEIVE NON-MULTIPLEXED HIGH-SPEED CONNECTION TO LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S, 4.096MBIT/S, OR 8.192MBIT/S
RxSERCLK = 2.048/4.096/8.192MHz XRT86VL3x RxSERCLK0 RxSER0 RxMSYNC0 RxSYNC0 Terminal Equipment RxSERCLKn RxSERn RxMSYNCn RxSYNCn Receive Payload Data Input Interface Chn N Receive Payload Data Input Interface Chn 0
Figure 79 shows the waveforms for connecting the Transmit non-multiplexed high-speed Input Interface block to local Terminal Equipment. Figure 80 shows the waveforms for connecting the Receive non-multiplexed high-speed Input Interface block to local Terminal Equipment. FIGURE 79. WAVEFORMS FOR CONNECTING THE TRANSMIT NON-MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT MVIP 2.048MBIT/S, 4.096MBIT/S, AND 8.192MBIT/S
TxMSYNC (2/4/8MHz) TxSERCLK (1.5 MHz) TxSERCLK (INV) TxSER TxSYNC(input) TxCHN[0]/TxSig Don't Care A B C D Don't Care A B C D Don't Care A B C D Don't Care
Don't Care
F
Don't Care
123456781234567812345678
Don't care
12345678
ABCD
Note: The following signals are not aligned with the signals shown above. The TxTSClk is derived from 1.544MHz transmit clock. TxCHCLK(INV) TxCHN[1]/TxFrTD Don't Care 12345678 Don't Care 12345678
71
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 80. WAVEFORMS FOR CONNECTING THE RECEIVE NON-MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT MVIP 2.048MBIT/S, 4.096MBIT/S, AND 8.192MBIT/S
RxSERCLK (2/4/8MHz) RxSER RxSYNC(input) RxCHN[0]/RxSig Don't Care A B C D Don't Care A B C D Don't Care A B C D Don't care
Don't Care
F
Don't Care
123456781234567812345678
Don't care
12345678
ABCD
Note: The following signals are not aligned with the signals shown above. The RxTSClk is derived from 1.544MHz transmit clock.
RxCHCLK(INV) RxCHN[1]/RxFrTD Don't Care 12345678 Don't Care 12345678
7.2.3
Multiplexed High-Speed Mode
When the Back-plane interface data rate is 12.352Mbit/s, 16.384Mbit/s, HMVIP 16.384Mbit/s, and H.100 16.384Mbit/s, the interface signals are all configured as inputs, except the receive serial data on RxSER and the multi frame sync pulse provided by the framer. The Back-plane Interface is processing data through TxSER0 or TxSER4 pins at 12.352Mbit/s or 16.384Mbit/s. The local Terminal Equipment multiplexes payload and signaling data of every four channels into one serial data stream. Payload and signaling data of Channel 03 are multiplexed onto the Transmit Serial Data pin of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4. Free-running clocks of 12.352MHz are supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of the framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit Input Clock. The Transmit Highspeed Back-plane Interface of the framer then latches incoming serial data at falling edge of the clock. Transmit 12.352 Bit-Multiplexed Mode The local Terminal Equipment maps four 1.544Mbit/s DS1 data streams into one 12.352Mbit/s serial data stream as described below: 1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is sent last. The table below shows bit-pattern of the first octet.
BIT PATTERN OF THE FIRST OCTET
BIT 0 BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X 2. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2. The first payload bit of Timeslot 0 of Channel 3 is sent last. After the first bits of Timeslot 0 of all four
72
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
channels are sent, it comes the second bit of Timeslot 0 of Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into the 12.352Mbit/s data stream.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y 3. The local Terminal Equipment also multiplexes signaling bits with payload bits and sends them together through the 12.352Mbit/s data stream. When the Terminal Equipment is sending the fifth payload bit of each channel, instead of sending it twice, it inserts the signaling bit A of that corresponding channel. Similarly, the sixth payload bit of a each channel is followed by the signaling bit B of that channel; the seventh payload bit is followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D. The following table illustrates how payload bits and signaling bits are multiplexed together into the 12.352Mbit/ s data stream.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y AY: The signaling bit A of Channel Y 4. Following the same rules of Step 2 and 3, the local Terminal Equipment continues to map the payload data and signaling data of four channels into a 12.352Mbit/s data stream.
73
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit position (F-bit of channel 0) of the multiplexed data stream with data from Channel 0-3 multiplexed together. The Transmit Single-frame Synchronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position (F-bit of Channel 4) of the data stream with data from Channel 4-7 multiplexed together. By sampling the HIGH pulse on the Transmit Single-frame Synchronization signal, the framer can position the beginning of the multiplexed DS1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchronization pulse. Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are de-multiplexed inside the XRT86VL3x and sent to each individual channel. These data will be processed by each individual framer and send to the LIU interface. The local Terminal Equipment provides a free-running 1.544MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. Figure 81 shows how to connect the Transmit multiplexed high-speed Input Interface block to local Terminal Equipment. Figure 85 shows the timing signal when the transmit framer is running at 12.352 Bit-Multiplexed Mode FIGURE 81. INTERFACING XRT86VL3X TRANSMIT TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S, HMVIP 16.384MBIT/S, AND H.100 16.384MBIT/S
XRT86VL38 TxSER0 TxINCLK0 (12/16MHz) TxSYNC0 TxSERCLK0 (1.544MHz) TxSERCLK1 (1.544MHz) TxSERCLK2 (1.544MHz) TxSERCLK3 (1.544MHz) Terminal Equipment Transmit Payload Data Input Interface Chn 0 Chn 1 Chn 2 Chn 3 Transmit Payload Data Input Interface Chn 4 Chn 5 Chn 6 Chn 7
TxSER4 TxINCLK4 (12/16MHz) TxSYNC4 TxSERCLK4 (1.544MHz) TxSERCLK5 (1.544MHz) TxSERCLK6 (1.544MHz) TxSERCLK7 (1.544MHz)
74
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 82. TIMING SIGNALS WHEN THE TRANSMIT FRAMER IS RUNNING AT 12.352 BIT-MULTIPLEXED MODE
TxInClk (12.352MHz) TxInClk (INV) TxSer TxSync(input) F0 F0 F1 F1 F2 F2 F3 F3 10 X 11 X 12 X 13 X 20 X 21 X 30 X 40 X 50 A0 51 A1 52 A2 53 A3 60 B0 61 B1 62 B2 63 B3
Transmit 16.384 Bit-Multiplexed Mode
Please refer to Figure 81 for how to interface the transmit payload data input interface block to the terminal equipment. The local Terminal Equipment maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s data stream as described below: 1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is sent last. The table below shows bit-pattern of the first octet.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X 2. After the first octet of data is sent, the local Terminal Equipment should insert seven octets (fifty-six bits) of "don't care" data into the outgoing data stream. 3. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2. The first payload bit of Timeslot 0 of Channel 3 is sent last. After the first bits of Timeslot 0 of all four channels are sent, it comes the second bit of Timeslot 0 of Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into the 16.384Mbit/s data stream.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y 4. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together through the 16.384Mbit/s data stream. When the Terminal Equipment is sending the fifth payload bit of each channel, instead of sending it twice, it inserts the signaling bit A of that corresponding channel. Similarly, the sixth payload bit of each channel is followed by the signaling bit B of that channel; the seventh payload bit is followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
75
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/ s data stream.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y AY: The signaling bit A of Channel Y 5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Terminal Equipment should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. Following the same rules of Step 2 to 5, the local Terminal Equipment stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/s data stream is thus created. The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit position (F-bit of channel 0) of the data stream with data from Channel 0-3 multiplexed together. The Transmit Single-frame Synchronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position (F-bit of Channel 4) of the data stream with data from Channel 4-7 multiplexed together. By sampling the HIGH pulse on the Transmit Single-frame Synchronization signal, the framer can position the beginning of the multiplexed DS1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchronization pulse. Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are de-multiplexed inside the XRT86VL3x and send to each individual channel. These data will be processed by each individual framer and send to LIU interface. The local Terminal Equipment provides a free-running 1.544MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed payload and signaling data to the transmit section of the device. Figure shows the timing signal when the transmit framer is running at 16.384 Bit-Multiplexed mode.
76
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 83. TIMING SIGNALS WHEN THE TRANSMIT FRAMER IS RUNNING AT 16.384 BIT-MULTIPLEXED MODE
TxInClk (16.384MHz) TxInClk (INV) TxSer TxSync(input) F0 F0 F1 F1 F2 F2 F3 F3 56 cycles 1 0 X 11 X 1 2 X 13 X 20 X 21 X 30 X 40 X 50 A0 51 A1 52 A2 53 A3
Transmit HMVIP / H.100 Byte-Multiplexed mode at 16.384 MHz
Please refer to Figure 81 for how to interface the transmit payload data input interface block to the terminal equipment. The local Terminal Equipment maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s data stream as described below: 1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is sent last. The table below shows bit-pattern of the first octet.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X 2. After the first octet of data is sent, the local Terminal Equipment should insert seven octets (fifty-six bits) of "don't care" data into the outgoing data stream. 3. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first payload bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel 0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel 3 are sent the last. After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload bits of Timeslot 1 of Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into the 16.384Mbit/s data stream.
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
77
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y 4. When the framer is running at HMVIP 16.384MBit/s byte-mulitplexed mode, signaling information is inserted from the TxSig/TxCHN[0] pin or from the TSCR register (0xn340-n357). When the local terminal is sending the fifth payload bit of one channel, signaling bit A of that corresponding channel is repeated and sent through the TxSig/TxCHN[0] pin; Similarly, signaling bit B, C, and D of the corresponding channel is repeated and sent through the TxSig/TxCHN[0] pin when the local terminal is providing the sixth, seventh, and eighth payload bit respectively, as shown in Figure . 5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Terminal Equipment should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream. 6. Following the same rules of Step 2 to 5, the local Terminal Equipment stuffs eight octets of "don't care" data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/s data stream is thus created. For HMVIP mode, the Transmit Single-frame Synchronization signal should pulse HIGH for four clock cycles (the last two bit positions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame boundary of the multiplexed data stream. For H.100 mode, TxSYNC should pulse HIGH for two clock cycles (the last bit position of the previous multiplexed frame and the first bit of the next multiplexed frame). The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH to identify the start of multiplexed data stream of Channel 0-3. The Transmit Single-frame Synchronization signal of Channel 4 pulses HIGH to identify the start of multiplexed data stream of Channel 4-7. By sampling the HIGH pulse on the Transmit Single-frame Synchronization signal, the framer can position the beginning of the multiplexed DS1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchronization pulse. Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are de-multiplexed inside the XRT86VL3x and send to each individual channel. These data will be processed by each individual framer and send to LIU interface. The local Terminal Equipment provides a free-running 1.544MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed payload and signaling data to the transmit section of the device.
78
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 84. TIMING SIGNALS WHEN THE TRANSMIT FRAMER IS RUNNING AT HMVIP / H.100 16.384MHZ MODE
TxInClk (16.384MHz) TxInClk (INV)
TxSer
73 73 83 83 F0 F0 F0 F0 F0 F0 F0 F0 Start of Frame C3C3 D3 D3 1 1 1 1 1 1 1 1
56 cycles 56 cycles
10 1 0 2 0 20 30 30 40 4 0 5 0 50 60 60
1 2 12
52 5 2
53 53 63 63 7 3 7 3 83 83
TxSig TxSync(input) HMVIP, negative sync TxSync(input) HMVIP, positive sync TxSync(input) H.100, negative sync TxSync(input) H.100, positive sync Delayer H.100 TxSync(input) H.100, negative sync TxSync(input) H.100, positive sync
Xy : X is the bit number and y is the channel number 0 0 0 0 0 0 0 0 A0 A0 B 0 B 0 00 A2 A2 A3 A3 B3 B3 C3 C3D3 D3
T1 Receive Multiplexed Mode
The interface consists of the following pins:
* Data Output (RxSer_n) * Receive Serial Clock Input signal (RxSerClk_n) * Receive Single-frame Synchronization Input signal (RxSync_n)
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 12.352Mbit/s or 16.384Mbit/s. It multiplexes payload and signaling data of every four channels into one data stream. Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of Channel 4. Free-running clocks of 12.352MHz or 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Receive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock. Figure 85 shows the interface of the Recieve Payload Data Output Interface Block to the Terminal Equipment. The multiplexed data output on RxSER_0 or RxSER_4 are very similar to the Multiplexed data input on TxSER_0 or TxSER_4 except when the receive framer is running at 12.352MHz or 16.384MHz Bit-Multiplexed mode. When the receive framer is running at 12MHz or 16MHz Bit-Multiplexed mode, the multiplexed data on RxSER_0 or RxSER_4 are return-to-zero data when the receive framer is processing the first four bits of each time slot data of each channel, as shown in Figure 86 and Figure 87. Figure 88 shows the timing signal when the receive framer is running at HMVIP or H.100 16.384 MHz mode.
79
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 85. INTERFACING XRT86VL3X RECEIVE TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S, HMVIP 16.384MBIT/S, AND H.100 16.384MBIT/S
XRT86VL38 RxSER0 Transmit RxSERCLK0 (12/16MHz) Payload Data Input RxSYNC0 Interface Chn 0 Chn 1 Chn 2 Chn 3 Terminal Equipment RxSER4 RxSERCLK (12/16MHz) RxSYNC4 Transmit Payload Data Input Interface Chn 4 Chn 5 Chn 6 Chn 7
.
FIGURE 86. WAVEFORMS FOR CONNECTING THE RECEIVE MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT 12.352MBIT/S MODE
RxSerClk (12.352MHz) RxSerClk (INV) RxSer RxSync(input) F0 F0 F1 F1 F2 F2 F3 F3 10 0 11 0 12 0 13 0 20 0 21 0 30 0 40 0 50 A0 51 A1 52 A2 53 A3 60 B0 61 B1 62 B2 63 B3
FIGURE 87. WAVEFORMS FOR CONNECTING THE RECEIVE MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT 16.384MBIT/S MODE
RxSerClk (16.384MHz) RxSerClk (INV) RxSer RxSync(input) F0 F0 F1 F1 F2 F2 F3 F3 56 cycles 10 0 11 0 12 0 13 0 20 0 21 0 30 0 40 0 50 A0 51 A1 52 A2 53 A3
80
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 88. WAVEFORMS FOR CONNECTING THE RECEIVE MULTIPLEXED HIGH-SPEED INPUT INTERFACE AT HMVIP AND H.100 16.384MBIT/S MODE
RxSerClk (16.384MHz) RxSerClk (INV)
RxSer
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3 Start of Frame C3 C3D3 D3 1 1 1 1 1 1 1 1
56 cycles 56 cycles
10 10 20 20 30 30 40 40 50 50 60 60
12 12
52 52
53 53 63 63 73 73 83 83
RxSig
Xy : X is the bit number and y is the channel number 0 0 0 0 0 0 0 0 A0 A0 B0 B0 00 A2 A2 A3 A3 B3 B3 C3 C3D3 D3
RxSync(input) H.100, negative sync RxSync(input) H.100, positive sync
RxSync(input) HMVIP, negative sync RxSync(input) HMVIP, positive sync
7.3
Brief Discussion of Robbed-bit Signaling in DS1 Framing Format
Signaling is required when dealing with voice and dial-up data services in DS1 applications. Traditionally, signaling is provided on a dial-up telephone line, across the talk-path. Bit robbing, or stealing the least significant bit (8th bit) in each of the twenty-four voice channels in the signaling frames allows enough bits to signal between the transmitting and receiving end. That is where the name Robbed-bit signaling comes from. These ends can be CPE to central office (CO) for switched services, or CPE to CPE for PBX-to-PBX connections. Signaling is used to tell the receiver where the call or route is destined. The signal is sent through switches along the route to a distant end. Common types of signals are:
* On hook * Off hook * Dial tone * Dialed digits * Ringing cycle * Busy tone
Robbed-bit Signaling is supported in three DS1 framing formats.
* Super-Frame (SF) * SLC(R)96 * Extended Super-Frame (ESF)
In Super-Frame or SLC(R)96 framing mode, frame number 6 and frame number 12 are signaling frames. In channelized DS1 applications, these frames are used to contain the signaling information. In frame number 6 and 12, the least significant bit of all twenty-four timeslots is 'robbed' to carry call state information. The bit in frame 6 is called the A bit and the bit in frame 12 is called the B bit. The combination of A and B defines the state of the call for the particular timeslot that these two bits are located in.
81
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FRAME NUMBER
SIGNALING BIT
6 12
A B
In Extended Super-Frame framing mode, frame number 6, 12, 18 and 24 are signaling frames. In these frames, the least significant bit of all twenty-four timeslots is 'robbed' to carry call state information. The bit in frame 6 is called the A bit, the bit in frame 12 is called the B bit, the bit in frame 18 is called the C bit and the bit in frame 24 is called the D bit. The combination of A, B, C and D defines the state of the call for the particular timeslot that these signaling bits are located in.
FRAME NUMBER
SIGNALING BIT
6 12 18 24
A B C D
7.3.1
Configure the framer to transmit Robbed-bit Signaling
The XRT86VL3x framer supports transmission of Robbed-bit Signaling in ESF, SF and SLC(R)96 framing formats. Signaling bits can be inserted into the outgoing DS1 frame through the following:
* Signaling data is inserted from Transmit Signaling Control Registers (TSCR) of each timeslot * Signaling data is inserted from TxSig_n pin * Signaling data is embedded into the input PCM data coming from the Terminal Equipment
7.3.2 Insert Signaling Bits from TSCR Register The four most significant bits of the Transmit Signaling Control Register (TSCR) of each timeslot can be used to store outgoing signaling data. The user can program these bits through the microprocessor access. If the XRT86VL3x framer is configured to insert signaling bits from the TSCR registers, the DS1 Transmit Framer block will strip off the least significant bits of each time slot in the signaling frames and replace it with the signaling bit stored inside the TSCR registers. The insertion of signaling bits into PCM data is done on a perchannel basis. In SF or SLC(R)96 mode, the user can control the XRT86VL3x framer to transmit no signaling (transparent), two-code signaling, or four-code signaling. Two-code signaling is done by substituting the least significant bit (LSB) of the specific channel in frame 6 and 12 with the content of the Signaling bit A of the specific TSCR register. Four-code signaling is done by substituting the LSB of channel data in frame 6 with the Signaling bit A and the LSB of channel data in frame 12 with the Signaling bit B of the specific channel's TSCR register. If sixteen-code signaling is selected in SF format, only the Signaling bit A and Signaling bit B information are used. In ESF mode, the user can control the XRT86VL3x framer to transmit no signaling (transparent) by disable signaling insertion, two-code signaling, four-code signaling or sixteen code signaling. Two-code signaling is done by substituting the least significant bit (LSB) of the specific channel in frame 6, 12, 18 and 24 with the content of the Signaling bit A of the specific TSCR register. Four-code signaling is done by substituting the LSB of channel data in frame 6 and frame 18 with the Signaling bit A and the LSB of channel data in frame 12 and frame 24 with the Signaling bit B of the specific channel's TSCR register.
82
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
Sixteen-code signaling is implemented by substituting the LSB of channel data in frames 6, 12, 18, and 24 with the content of Signaling bit A, B, C, and D of TSCR register respectively. In N or T1DM modes, no robbed-bit signaling is allowed and the transmit data stream remains intact. The table below shows the four most significant bits of the Transmit Signaling Control Register.
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (ADDRESS = 0XN340H - 0XN357H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
7 6 5 4
Signaling Bit A Signaling Bit B Signaling Bit C Signaling Bit D
R/W R/W R/W R/W
This bit is used to store Signaling Bit A that is sent as the least significant bit of timeslot of frame number 6. This bit is used to store Signaling Bit B that is sent as the least significant bit of timeslot of frame number 12. This bit is used to store Signaling Bit C that is sent as the least significant bit of timeslot of frame number 18. This bit is used to store Signaling Bit D that is sent as the least significant bit of timeslot of frame number 24.
7.3.3
Insert Signaling Bits from TxSig_n Pin
The XRT86VL3x framer can be configured to insert signaling bits provided by external equipment through the TxSig_n pins. This pin is a multiplexed I/O pin with two functions:
* TxCHN[0]_n - Transmit Timeslot Number Bit [0] Output pin * TxSig_n - Transmit Signaling Input pin
When the Transmit Fractional DS1 bit of the Transmit Interface Control Register (TICR) is set to 0, this pin is configured as TxTSb[0]_n pin, it outputs bit 0 of the timeslot number of the DS1 PCM data that is transmitting. When the Transmit Fractional DS1 bit of the Transmit Interface Control Register (TICR) is set to 1, this pin is configured as TxSig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound DS1 frames. Figure 89 below is a timing diagram of the TxSig_n input pin. Please note that the Signaling Bit A of a certain timeslot coincides with Bit 4 of the PCM data; Signaling Bit B coincides with Bit 5 of the PCM data; Signaling Bit C coincides with Bit 6 of the PCM data and Signaling Bit D coincides with Bit 7 (LSB) of the PCM data. FIGURE 89. TIMING DIAGRAM OF THE TXSIG_N INPUT
83
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The table below shows configurations of the Transmit Fractional DS1 bit of the Transmit Interface Control Register (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR)(ADDRESS = 0XN120H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
4
Transmit Fractional DS1
R/W
This READ/WRITE bit-field permits the user to determine which one of the two functions the multiplexed I/O pin of TxTSb[0]_n/TxSig_n is spotting. 0 - This pin is configured as TxTSb[0]_n pin, it outputs bit 0 of the timeslot number of the DS1 PCM data that is transmitting. 1 - This pin is configured as TxSig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound DS1 frames
84
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 8.0 ALARMS AND ERROR CONDITIONS The XRT86VL3x T1/J1/E1 Framer can be configured to monitor quality of received DS1 frames. It can generate error indicators if the local receive framer has received error frames from the remote terminal. If corresponding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. Upon microprocessor interruption, the user can intervene by looking into the error conditions. At the same time, the user can configure the XRT86VL3x framer to transmit alarms and error indications to remote terminal. Different alarms and error indications will be transmitted depending on the error condition. The section below gives a brief discussion of the error conditions that can be detected by the XRT86VL3x framer and error indications that will be generated.
8.1 AIS Alarm
REV. 1.2.0
As we discussed before, transmission of Alarm Indication Signal (AIS) or Blue Alarm by the intermediate node indicates that the equipment is still functioning but unable to offer services. It is an all ones (except for framing bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing synchronization. The XRT86VL3x framer can detect two types of AIS in DS1 mode:
* Framed AIS * Unframed AIS
Unframed AIS is an all ones pattern. If unframed AIS is sent, the equipment further down the line will be able to maintain timing synchronization and be able to recover clock from the received AIS signal. However, due to the lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and will declare Loss of Frame (LOF). On the other hand, the payload portion of a framed AIS pattern is all ones. However, a framed AIS pattern still has correct framing bits. Therefore, the equipment further down the line can still maintain frame synchronization as well as timing synchronization. In this case, no LOF or Red alarm will be declared. The Alarm indication logic within the Receive Framer block of the XRT86VL3x framer monitors the incoming DS1 frames for AIS. AIS alarm condition are detected and declared according to the following procedure: 1. The incoming DS1 frames are monitored for AIS detection. AIS detection is defined as an unframed or framed pattern with less than three zeros in two consecutive frames. 2. An AIS detection counter within the Receive Framer block of the XRT86VL3x counts the occurrences of AIS detection over a 6 ms interval. It will indicate a valid AIS flag when twenty-two or more of a possible twenty-four AIS are detected. 3. Each 6 ms interval with a valid AIS flag increments a flag counter which declares AIS alarm when 255 valid flags have been collected. Therefore, AIS condition has to be persisted for 1.53 seconds before AIS alarm condition is declared by the XRT86VL3x framer. If there is no valid AIS flag over a 6ms interval, the Alarm indication logic will decrement the flag counter. The AIS alarm is removed when the counter reaches 0. That is, AIS alarm will be removed if over 1.53 seconds, there is no valid AIS flag.
85
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The Alarm Indication Signal Detection Select bits of the Alarm Generation Register (AGR) enable the two types of AIS detection that are supported by the XRT86VL3x framer. The table below shows configurations of the Alarm Indication Signal Detection Select bits of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR) (ADDRESS = 0XN108H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1-0
AIS Detection Select
R/W
00 - AIS alarm detection is disabled.When this bit is set to 01:Detection of unframed AIS alarm of all ones pattern is enabled. 10 - AIS alarm detection is disabled.When this bit is set to 00:Detection of framed AIS alarm of all ones pattern except for framing bits is enabled.
If detection of unframed or framed AIS alarm is enabled by the user and if AIS is present in the incoming DS1 frame, the XRT86VL3x framer can generate a Receive AIS State Change interrupt associated with the setting of Receive AIS State Change bit of the Alarm and Error Status Register to one. To enable the Receive AIS State Change interrupt, the Receive AIS State Change Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER) have to be set to one. In addition, the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one. The table below shows configurations of the Receive AIS State Change Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (ADDRESS = 0XNB03H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1
Receive AIS State Change Interrupt Enable
R/W
0 - The Receive AIS State Change interrupt is disabled. 1 - The Receive AIS State Change interrupt is enabled.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (ADDRESS = 0XNB01H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1
Alarm and Error Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is disabled. 1 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is enabled.
When these interrupt enable bits are set and AIS is present in the incoming DS1 frame, the XRT86VL3x framer will declare AIS by doing the following:
* Set the read-only Receive AIS State bit of the Alarm and Error Status Register (AESR) to one indicating
there is AIS alarm detected in the incoming DS1 frame.
* Set the Receive AIS State Change bit of the Alarm and Error Status Register to one indicating there is a
change in state of AIS. This status indicator is valid until the Framer Interrupt Status Register is read. Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators.
86
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
The table below shows the Receive AIS State Change status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1
Receive AIS State Change
RUR / WC
0 - There is no change of AIS state in the incoming DS1 payload data. 1 - There is change of AIS state in the incoming DS1 payload data.
The Receive AIS State bit of the Alarm and Error Status Register (AESR), on the other hand, is a read-only bit indicating there is AIS alarm detected in the incoming DS1 frame. The table below shows the Receive AIS State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
6
Receive AIS State
R
0 - There is no AIS alarm condition detected in the incoming DS1 payload data. 1 - There is AIS alarm condition detected in the incoming DS1 payload data.
8.2
Red Alarm
The Alarm indication logic within the Receive Framer block of the XRT86VL3x framer monitors the incoming DS1 frames for red alarm or Loss of Frame (LOF) condition. Red alarm condition are detected and declared according to the following procedure: 1. The red alarm is detected by monitoring the occurrence of Loss of Frame (LOF) over a 6 ms interval. 2. An LOF valid flag will be posted on the interval when one or more LOF occurred during the interval. 3. Each interval with a valid LOF flag increments a flag counter which declares RED alarm when 63 valid intervals have been accumulated. 4. An interval without valid LOF flag decrements the flag counter. The Red alarm is removed when the counter reaches zero. If LOF condition is present in the incoming DS1 frame, the XRT86VL3x framer can generate a Receive Red Alarm State Change interrupt associated with the setting of Receive Red Alarm State Change bit of the Alarm and Error Status Register to one. To enable the Receive Red Alarm State Change interrupt, the Receive Red Alarm State Change Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one. The table below shows configurations of the Receive Red Alarm State Change Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (ADDRESS = 0XNB03H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
2
Receive Red Alarm State Change Interrupt Enable
R/W
0 - The Receive Red Alarm State Change interrupt is disabled. No Receive Red Alarm interrupt will be generated upon detection of Red Alarm condition. 1 - The Receive Red Alarm State Change interrupt is enabled. Receive Red Alarm interrupt will be generated upon detection of Red Alarm condition.
87
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (ADDRESS = 0XNB01H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1
Alarm and Error Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is disabled. 1 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is enabled.
When these interrupt enable bits are set and Red Alarm is present in the incoming DS1 frame, the XRT86VL3x framer will declare Red Alarm by doing the following:
* Set the read-only Receive Red Alarm State bit of the Alarm and Error Status Register (AESR) to one
indicating there is Red Alarm detected in the incoming DS1 frame.
* Set the Receive Red Alarm State Change bit of the Alarm and Error Status Register to one indicating there is
a change in state of Red Alarm. This status indicator is valid until the Framer Interrupt Status Register is read. Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. The table below shows the Receive Red Alarm State Change status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
2
Receive Red Alarm State Change
RUR / WC
0 - There is no change of Red Alarm state in the incoming DS1 payload data. 1 - There is change of Red Alarm state in the incoming DS1 payload data.
The Receive Red Alarm State bit of the Alarm and Error Status Register (AESR), on the other hand, is a readonly bit indicating there is Red Alarm detected in the incoming DS1 frame. The table below shows the Receive Red Alarm State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
7
Receive Red Alarm State
R
0 - There is no Red Alarm condition detected in the incoming DS1 payload data. 1 - There is Red Alarm condition detected in the incoming DS1 payload data.
8.3
Yellow Alarm
The Alarm indication logic within the Receive Framer block of the XRT86VL3x framer monitors the incoming DS1 frames for Yellow Alarm condition. The yellow alarm is detected and declared according to the following procedure:
88
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
1. Monitor the occurrence of Yellow Alarm pattern over a 6 ms interval. A YEL valid flag will be posted on the interval when Yellow Alarm pattern occurred during the interval. 2. Each interval with a valid YEL flag increments a flag counter which declares YEL alarm when 80 valid intervals have been accumulated. 3. An interval without valid YEL flag decrements the flag counter. The YEL alarm is removed when the counter reaches zero. If Yellow Alarm condition is present in the incoming DS1 frame, the XRT86VL3x framer can generate a Receive Yellow Alarm State Change interrupt associated with the setting of Receive Yellow Alarm State Change bit of the Alarm and Error Status Register to one. To enable the Receive Yellow Alarm State Change interrupt, the Receive Yellow Alarm State Change Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one. The table below shows configurations of the Receive Yellow Alarm State Change Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (ADDRESS = 0XNB03H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
0
Receive Yellow Alarm State Change Interrupt Enable
R/W
0 - The Receive Yellow Alarm State Change interrupt is disabled. Any state change of Receive Yellow Alarm will not generate an interrupt. 1 - The Receive Yellow Alarm State Change interrupt is enabled. Any state change of Receive Yellow Alarm will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (ADDRESS = 0XNB01H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1
Alarm and Error Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is disabled. 1 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is enabled.
When these interrupt enable bits are set and Yellow Alarm is present in the incoming DS1 frame, the XRT86VL3x framer will declare Yellow Alarm by doing the following:
* Set the read-only Receive Yellow Alarm State bit of the Alarm and Error Status Register (AESR) to one
indicating there is Yellow Alarm detected in the incoming DS1 frame.
* Set the Receive Yellow Alarm State Change bit of the Alarm and Error Status Register to one indicating there
is a change in state of Yellow Alarm. This status indicator is valid until the Framer Interrupt Status Register is read. Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators.
89
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
The table below shows the Receive Yellow Alarm State Change status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR)(ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
0
Receive Yellow Alarm State Change
RUR / WC
0 - There is no change of Yellow Alarm state in the incoming DS1 payload data. 1 - There is change of Yellow Alarm state in the incoming DS1 payload data.
The table below shows the Receive AIS State Change status bits of the Alarm and Error Status Register. The Receive Yellow Alarm State bit of the Alarm and Error Status Register (AESR), on the other hand, is a read-only bit indicating there is Yellow Alarm detected in the incoming DS1 frame. The table below shows the Receive Yellow Alarm State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
5
Receive Yellow Alarm State
R
0 - There is no Yellow Alarm condition detected in the incoming DS1 payload data. 1 - There is Yellow Alarm condition detected in the incoming DS1 payload data.
8.4
Bipolar Violation
The line coding for the DS1 signal should be bipolar. That is, a binary "0" is transmitted as zero volts while a binary "1" is transmitted as either a positive or negative pulse, opposite in polarity to the previous pulse. A Bipolar Violation or BPV occurs when the alternate polarity rule is violated. The Alarm indication logic within the Receive Framer block of the XRT86VL3x framer monitors the incoming DS1 frames for Bipolar Violations. If a Bipolar Violation is present in the incoming DS1 frame, the XRT86VL3x framer can generate a Receive Bipolar Violation interrupt associated with the setting of Receive Bipolar Violation bit of the Alarm and Error Status Register to one. To enable the Receive Bipolar Violation interrupt, the Receive Bipolar Violation Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one. The table below shows configurations of the Receive Bipolar Violation Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (ADDRESS = 0XNB03H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
3
Receive Bipolar Violation Interrupt Enable
R/W
0 - The Receive Bipolar Violation interrupt is disabled. Occurrence of one or more bipolar violations will not generate an interrupt. 1 - The Receive Bipolar Violation interrupt is enabled. Occurrence of one or more bipolar violations will generate an interrupt.
90
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (ADDRESS = 0XNB01H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1
Alarm and Error Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is disabled. 1 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is enabled.
When these interrupt enable bits are set and one or more Bipolar Violations are present in the incoming DS1 frame, the XRT86VL3x framer will declare Receive Bipolar Violation by doing the following:
* Set the Receive Bipolar Violation bit of the Alarm and Error Status Register to one indicating there are one or
more Bipolar Violations. This status indicator is valid until the Framer Interrupt Status Register is read. Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. The table below shows the Receive Bipolar Violation status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
3
Receive Bipolar Violation State Change
RUR / WC
0 - There is no change of Bipolar Violation state in the incoming DS1 payload data. 1 - There is change of Bipolar Violation state in the incoming DS1 payload data.
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (ADDRESS = 0XNB03H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
4
Receive Loss of Signal Interrupt Enable
R/W
0 - The Receive Loss of Signal interrupt is disabled. Occurrence of Loss of Signals will not generate an interrupt. 1 - The Receive Loss of Signal interrupt is enabled. Occurrence of Loss of Signals will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (ADDRESS = 0XNB01H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
1
Alarm and Error Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is disabled. 1 - Every interrupt generated by the Alarm and Error Interrupt Status Register (AEISR) is enabled.
91
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
When these interrupt enable bits are set and one or more Loss of Signals are present in the incoming DS1 frame, the XRT86VL3x framer will declare Receive Loss of Signal by doing the following:
* Set the Receive Loss of Signal bit of the Alarm and Error Status Register to one indicating there is one or
more Loss of Signals. This status indicator is valid until the Framer Interrupt Status Register is read. Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators. The table below shows the Receive Loss of Signal status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (ADDRESS = 0XNB02H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
4
Receive Loss of Signal State
RUR / WC
0 - There is no change of Loss of Signal state in the incoming DS1 payload data. 1 - There is change of Loss of Signal state in the incoming DS1 payload data.
8.5
E1 Brief discussion of alarms and error conditions
As defined in E1 specification, alarm conditions are created from defects. Defects are momentary impairments present on the E1 trunk. If a defect is present for a sufficient amount of time (called the integration time), then the defect becomes an alarm. Once an alarm is declared, the alarm is present until after the defect clears for a sufficient period of time. The time it takes to clear an alarm is called the de-integration time. Alarms are used to detect and warn maintenance personnel of problems on the E1 trunk. There are three types of alarms:
* Red alarm or Service Alarm Indication (SAI) Signal * Blue alarm or Alarm Indication Signal (AIS) * Yellow alarm or Remote Alarm Indication (RAI) Signal
To explain the error conditions and generation of different alarms, let us create a simple E1 system model. In this model, an E1 signal is sourced from the Central Office (CO) through a Repeater to the Customer Premises Equipment (CPE). At the same time, an E1 signal is routed from the CPE to the Repeater and back to the Central Office. Figure 90 below shows the simple E1 system model.
92
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 90. SIMPLE DIAGRAM OF E1 SYSTEM MODEL
REV. 1.2.0
CO
Repeater
CPE
E1 Receive Framer Block
E1 Transmit Section
E1 Receive Section
E1 Receive Framer Block
E1 Transmit Framer Block
E1 Receive Section
E1 Transmit Section
E1 Transmit Framer Block
Simple E1 System Model
When the E1 system runs normally, that is, when there is no Loss of Signal (LOS) or Loss of Frame (LOF) detected in the line, no alarm will be generated. Sometimes, intermittent outburst of electrical noises on the line might result in Bipolar Violation or bit errors in the incoming signals, but these errors in general will not trigger the equipment to generate alarms. They will, depending on the system requirements, trigger the framer to generate interrupts that would cause the local microprocessor to create performance reports of the line. Now, consider a case in which the E1 line from the CO to the Repeater is broken or interrupted, resulting in completely loss of incoming data or severely impaired signal quality. Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the Repeater will generate an internal Red Alarm, also known as the Service Alarm Indication. This alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. When the Repeater is in the Red Alarm state, it will transmit the Yellow Alarm to the CO indicating the loss of an incoming signal or loss of frame synchronization. This Yellow Alarm informs the CO that there is a problem further down the line and its transmission is not being received at the Repeater. Figure 91 below illustrates the scenario in which the E1 connection from the CO to the Repeater is broken.
93
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 91. GENERATION OF YELLOW ALARM BY THE REPEATER UPON DETECTION OF LINE FAILURE
Repeater declares Red Alarm internally Repeater generates Yellow Alarm to CO
CO
Repeater
CPE
E1 Receive Framer Block
Yellow Alarm
E1 Transmit Section
E1 Receive Section
E1 Receive Framer Block
E1 Transmit Framer Block
E1 Receive Section
E1 Transmit Section
E1 Transmit Framer Block
The E1 line is broken
The Repeater will also transmit a Blue Alarm, also known as Alarm Indication Signal (AIS) to the CPE. Blue alarm is an all ones pattern indicating that the equipment is functioning but unable to offer service due to failures originated from remote side. It is sent such that the equipment downstream will not lose clock synchronization even though no meaningful data is received. Figure 92 below illustrates this scenario in which the Repeater is sending an AIS to the CPE upon detection of line failure from the CO.
94
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 92. GENERATION OF AIS BY THE REPEATER UPON DETECTION OF LINE FAILURE
Repeater declares Red Alarm internally Repeater generates Yellow Alarm to CO
REV. 1.2.0
CO
Repeater
CPE
E1 Receive Framer Block
Yellow Alarm
E1 Transmit Section
E1 Receive Section
E1 Receive Framer Block
E1 Transmit Framer Block
E1 Receive Section
E1 Transmit Section
AIS
E1 Transmit Framer Block
The E1 line is broken
Repeater generates AIS to CPE
Now, the CPE uses the AIS signal sent by the Repeater to recover received clock and remain in synchronization with the system. Upon detecting the incoming AIS signal, the CPE will generate a Yellow Alarm automatically to the Repeater to indicate the loss of incoming data. Figure 93 below illustrates this scenario in which the Repeater is sending an AIS to the CPE and the CPE is sending a Yellow Alarm back to the Repeater.
95
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 93. GENERATION OF YELLOW ALARM BY THE CPE UPON DETECTION OF AIS ORIGINATED BY THE REPEATER
Repeater declares Red Alarm internally Repeater generates Yellow Alarm to CO
CPE detects AIS and generates Yellow Alarm to Repeater
CO
Repeater
CPE
E1 Receive Framer Block
Yellow Alarm
E1 Transmit Section
E1 Receive Section
Yellow Alarm
E1 Receive Framer Block
E1 Transmit Framer Block
E1 Receive Section
E1 Transmit Section
AIS
E1 Transmit Framer Block
The E1 line is broken
Repeater generates AIS to CPE
Next, let us consider the scenario in which the signaling and data link channel (the time slot 16) of an E1 line between a far-end terminal (for example, the CO) and a near-end terminal (for example, the repeater) is impaired. In this case, the CAS signaling data received by the repeater is corrupted. The Repeater will then send an all ones pattern in time slot 16 (AIS16) downstream to the CPE. The repeater will also generate a CAS Multi-frame Yellow Alarm upstream to the CO to indicate the loss of CAS Multi-frame synchronization. Figure 94 below illustrates this scenario in which the Repeater is sending an "AIS16" pattern to the CPE while sending a CAS Multi-frame Yellow Alarm to the CO.
96
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 94. GENERATION OF CAS MULTI-FRAME YELLOW ALARM AND AIS16 BY THE REPEATER
Repeater generates CAS Multi-frame Yellow Alarm to CO
REV. 1.2.0
CO
CAS Multiframe Yellow Alarm
Repeater
CPE
E1 Receive Framer Block
E1 Transmit Section
E1 Receive Section
E1 Receive Framer Block
E1 Transmit Framer Block
E1 Receive Section
E1 Transmit Section
AIS16
E1 Transmit Framer Block
The timeslot 16 of an E1 line is iimpaired
Repeater generates AIS16 to CPE
The CPE, upon detecting the incoming AIS16 signal, will generate a CAS Multi-frame Yellow Alarm to the Repeater to indicate the loss of CAS Multi-frame synchronization. Figure 95 below illustrates the CPE sending a CAS Multi-frame Yellow Alarm back to the Repeater.
97
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 95. GENERATION OF CAS MULTI-FRAME YELLOW ALARM BY THE CPE UPON DETECTION OF "AIS16" PATTERN SENT BY THE REPEATER
CPE detects AIS16 and generates CAS Multi-frame Yellow Alarm to Repeater
Repeater generates CAS Multi-frame Yellow Alarm to CO
CO
CAS Multiframe Yellow Alarm
Repeater
CAS Multiframe Yellow Alarm
CPE
E1 Receive Framer Block
E1 Transmit Section
E1 Receive Section
E1 Receive Framer Block
E1 Transmit Framer Block
E1 Receive Section
E1 Transmit Section
AIS16
E1 Transmit Framer Block
The timeslot 16 of an E1 line is iimpaired
Repeater generates AIS16 to CPE
In summary, AIS or Blue Alarm is sent by a piece of E1 equipment downstream indicating that the incoming signal from upstream is lost. Yellow Alarm is sent by a piece of E1 equipment upstream upon detection of Loss of Signal, Loss of Frame or when it is receiving AIS. Similarly, an "AIS16" pattern is sent by a piece of E1 equipment downstream indicating that the incoming data link channel from upstream is damaged. The CAS Multi-frame Yellow Alarm is sent by a piece of E1 equipment upstream upon detection of Loss of CAS Multi-frame synchronization or when it is receiving an "AIS16" pattern. 8.5.1 How to configure the framer to transmit AIS
As we discussed in the previous section, Alarm Indication Signal (AIS) or Blue Alarm is transmitted by the intermediate node to indicate that the equipment is still functioning but unable to offer services. It is an all ones (except for framing bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing synchronization. The XRT86VL3x framer can generate three types of AIS when it is running in E1 format:
* Framed AIS * Unframed AIS * AIS16
Unframed AIS is an all ones pattern. If unframed AIS is sent, the equipment further down the line will be able to maintain timing synchronization and be able to recover clock from the received AIS signal. However, due to the lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and will declare Loss of Frame (LOF).
98
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
On the other hand, the payload portion of a framed AIS pattern is all ones. However, a framed AIS pattern still has correct framing bits. Therefore, the equipment further down the line can still maintain frame synchronization as well as timing synchronization. In this case, no LOF or Red alarm will be declared. "AIS16" is an AIS alarm that is supported only in E1 framing format. It is an all ones pattern in time slot 16 of each E1 frame. As we mentioned before, time slot 16 is usually used for signaling and data link in E1, therefore, an "AIS16" alarm is transmitted by the intermediate node to indicate that the data link channel is having a problem. Since all the other thirty one time slots are still transmitting normal data (that is, framing information and PCM data), the equipment further down the line can still maintain frame synchronization, timing synchronization as well as receive PCM data. In this case, no LOF or Red alarm will be declared by the equipment further down the line. However, a CAS Multi-frame Yellow Alarm will be sent by the equipment further down the line to indicate the loss of CAS Multi-frame alignment. The Transmit Alarm Indication Signal Select bits of the Alarm Generation Register (AGR) enable the three types of AIS transmission that are supported by the XRT86VL3x framer. The table below shows configurations of the Transmit Alarm Indication Signal Select bits of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR) (ADDRESS = 0XN108H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
3-2
Transmit AIS Select
R/W
These READ/WRITE bit-fields allows the user to choose which one of the three AIS pattern supported by the XRT86VL3x framer will be transmitted. 00 - No AIS alarm is generated. 01 - Enable unframed AIS alarm of all ones pattern. 11 - AIS16 pattern is generated. Only time slot 16 is carrying the all ones pattern. The other time slots still carry framing and PCM data. 11 - Enable framed AIS alarm of all ones pattern except for framing bits.
8.5.2
How to configure the framer to generate Red Alarm
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the Repeater will generate an internal Red Alarm when enabled. This alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. The Loss of Frame Declaration Enable bit of the Alarm Generation Register (AGR) enable the generation of Red Alarm. The table below shows configurations of the of Frame Declaration Enable bit of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR) (ADDRESS = 0XN108H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
6
Loss of Frame Declaration Enable
R/W
This READ/WRITE bit-field permits the framer to declare Red Alarm in case of Loss of Frame Alignment (LOF). When receiver module of the framer detects Loss of Frame Alignment in the incoming data stream, it will generate a Red Alarm. The framer will also generate an RxLOFs interrupt to notify the microprocessor that an LOF condition is occurred. A Yellow Alarm is then returned to the remote transmitter to report that the local receiver detects LOF. 0 - Red Alarm declaration is disabled. 1 - Red Alarm declaration is enabled.
8.5.3
How to configure the framer to transmit Yellow Alarm
The XRT86VL3x framer supports transmission of both Yellow Alarm and CAS Multi-frame Yellow Alarm in E1 mode.
99
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the receiver will transmit the Yellow Alarm back to the source indicating the loss of an incoming signal. This Yellow Alarm informs the source that there is a problem further down the line and its transmission is not being received at the destination. On the other hand, upon detection of Loss of CAS Multi-frame alignment pattern, the receiver section of the XRT86VL3x framer will transmit a CAS Multi-frame Yellow Alarm back to the source indicating the Loss of CAS Multi-frame synchronization. The Yellow Alarm Generation Select bits of the Alarm Generation Register (AGR) enable transmission of different types of Yellow alarm that are supported by the XRT86VL3x framer. 8.5.4 Transmit Yellow Alarm
The Yellow Alarm bits are located at bit 2 of time slot 0 of non-FAS frames. A logic one of this bit denotes the Yellow Alarm and a logic zero of this bit denotes normal operation. The XRT86VL3x supports transmission of Yellow Alarm automatically or manually. When the Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 01, the Yellow Alarm bit is transmitted by echoing the received FAS alignment pattern. If the correct FAS alignment is received, the Yellow Alarm bit is set to zero. If the FAS alignment pattern is missing or corrupted, the Yellow Alarm bit is set to one while Loss of Frame Synchronization is declared. When the Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 10, the Yellow Alarm bit is transmitted as zero. When the Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 11, the Yellow Alarm bit is transmitted as one. 8.5.5 Transmit CAS Multi-frame Yellow Alarm
Within the sixteen-frame CAS Multi-frame, the CAS Multi-frame Yellow Alarm bits are located at bit 6 of time slot 16 of frame number 0. A logic one of this bit denotes the CAS Multi-frame Yellow Alarm and a logic zero of this bit denotes normal operation. The XRT86VL3x supports transmission of CAS Multi-frame Yellow Alarm automatically or manually. When the CAS Multi-frame Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 01, the CAS Multi-frame Yellow Alarm bit is transmitted by echoing the received CAS Multi-frame alignment pattern (the four zeros pattern). If the correct CAS Multi-frame alignment is received, the CAS Multi-frame Yellow Alarm bit is set to zero. If the CAS Multi-frame alignment pattern is missing or corrupted, the CAS Multi-frame Yellow Alarm bit is set to one while Loss of CAS Multi-frame Synchronization is declared. When the CAS Multi-frame Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 10, the CAS Multi-frame Yellow Alarm bit is transmitted as zero. When the CAS Multi-frame Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 11, the CAS Multi-frame Yellow Alarm bit is transmitted as one.
100
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
8.6 T1 Brief discussion of alarms and error conditions
REV. 1.2.0
As defined in ANSI T1.231 specification, alarm conditions are created from defects. Defects are momentary impairments present on the DS1 trunk. If a defect is present for a sufficient amount of time (called the integration time), then the defect becomes an alarm. Once an alarm is declared, the alarm is present until after the defect clears for a specified period of time. The time it takes to clear an alarm is called the de-integration time. Alarms are used to detect and warn maintenance personnel of problems on the DS1 trunk. There are three types of alarms:
* Red alarm or Service Alarm Indication (SAI) Signal * Blue alarm or Alarm Indication Signal (AIS) * Yellow alarm or Remote Alarm Indication (RAI) Signal
A simple DS1 system model is shown in Figure 96 to explain the error conditions and generation of different alarms, let us create. In this model, a DS1 signal is sourced from the Central Office (CO) through a Repeater to the Customer Premises Equipment (CPE). At the same time, a DS1 signal is routed from the CPE to the Repeater and back to the Central Office. FIGURE 96. SIMPLE DIAGRAM OF DS1 SYSTEM MODEL
CO
Repeater
CPE
DS1 Receive Framer Block
DS1 Transmit Section
DS1 Receive Section
DS1 Receive Framer Block
DS1 Transmit Framer Block
DS1 Receive Section
DS1 Transmit Section
DS1 Transmit Framer Block
Simple DS1 System Model
When the DS1 system runs normally, i.e., when there is no Loss of Signal (LOS) or Loss of Frame (LOF) detected in the line, no alarm will be generated. Sometimes, intermittent outburst of electrical noises on the line might result in Bipolar Violation or bit errors in the incoming signals, but these errors in general will not trigger the equipment to generate alarms. They will at most trigger the framer to generate interrupts which would cause the local microprocessor to interrupt as well as add statistics in the performance monitoring accumulator registers. Now, consider a case in which the DS1 line from the Repeater to CPE is broken or interrupted, resulting in a complete loss of incoming data or a severely impaired signal quality. Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the CPE will generate an internal Red Alarm, also known as the Service Alarm Indication. This alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. When the CPE is in the Red Alarm state, it will transmit the Yellow Alarm to the Repeater indicating the loss of an incoming signal or loss of frame synchronization. This Yellow Alarm informs the Repeater that there is a
101
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
problem further down the line and its transmission is not being received at the CPE. The Figure below illustrates the scenario in which the DS1 connection from the Repeater to CPE is broken. FIGURE 97. GENERATION OF YELLOW ALARM BY THE CPE UPON DETECTION OF LINE FAILURE
CPE declares Red Alarm internally
CO
Repeater
CPE
DS1 Receive Framer Block
DS1 Transmit Section
DS1 Receive Section
Yellow Alarm
DS1 Receive Framer Block
DS1 Transmit Framer Block
DS1 Receive Section
DS1 Transmit Section
DS1 Transmit Framer Block
The DS1 line is broken
The Repeater, upon detection of Yellow Alarm originated from the CPE, will transmit a Blue Alarm, also known as Alarm Indication Signal (AIS) to the CO. Blue alarm is an all ones pattern indicating that the equipment is functioning but unable to offer service due to failures originated from remote side. It is sent such that the equipment downstream will not lose clock synchronization even though no meaningful data is received. The Figure below illustrates this scenario in which the Repeater is sending an AIS to CO upon detection of Yellow alarm originated from the CPE.
102
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Generation of AIS by the Repeater upon detection of Yellow Alarm originated by the CPE
Repeater detects Yellow alarm and generate AIS to CO
REV. 1.2.0
CPE declares Red Alarm internally
CO
Repeater
CPE
DS1 Receive Framer Block
AIS
DS1 Transmit Section
DS1 Receive Section
Yellow Alarm
DS1 Receive Framer Block
DS1 Transmit Framer Block
DS1 Receive Section
DS1 Transmit Section
DS1 Transmit Framer Block
The DS1 line is broken
Now let us consider another scenario in which the DS1 line between CO and the Repeater is broken. Again, upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the Repeater will generate an internal Red Alarm. This alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. The Repeater will also send an all ones AIS pattern downstream to the CPE and a Yellow Alarm back to the CO. The CPE uses the AIS signal to recover received clock and remain in synchronization with the system. Upon detecting the incoming AIS signal, the CPE will generate a Yellow Alarm to the Repeater to indicate the loss of incoming signal. The Figure below illustrates this scenario in which the Repeater is sending an AIS to the CPE and the CPE is sending a Yellow Alarm back to the Repeater.
103
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 98. GENERATION OF YELLOW ALARM BY THE CPE UPON DETECTION OF AIS ORIGINATED BY THE REPEATER
Repeater declares Red Alarm internally
CO
Repeater
CPE
DS1 Receive Framer Block
DS1 Transmit Section
DS1 Receive Section
Yellow Alarm
DS1 Receive Framer Block
DS1 Transmit Framer Block
DS1 Receive Section
DS1 Transmit Section
AIS
DS1 Transmit Framer Block
The DS1 line is broken
Repeater detects Yellow alarm and generate AIS to CO
8.6.1
How to configure the framer to transmit AIS
As we discussed in the previous section, Alarm Indication Signal (AIS) or Blue Alarm is transmitted by the intermediate node to indicate that the equipment is still functioning but unable to offer services. It is an all ones (except for framing bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing synchronization. The XRT86VL3x framer can generate two types of AIS:
* Framed AIS * Unframed AIS
Unframed AIS is an all ones pattern. If unframed AIS is sent, the equipment further down the line will be able to maintain timing synchronization and be able to recover clock from the received AIS signal. However, due to the lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and will declare Loss of Frame (LOF). On the other hand, the payload portion of a framed AIS pattern is all ones. However, a framed AIS pattern still has correct framing bits. Therefore, the equipment further down the line can still maintain frame synchronization as well as timing synchronization. In this case, no LOF or Red alarm will be declared. The Transmit Alarm Indication Signal Select bits of the Alarm Generation Register (AGR) enable the two types of AIS transmission that are supported by the XRT86VL3x framer. The table below shows configurations of the Transmit Alarm Indication Signal Select bits of the Alarm Generation Register (AGR)
104
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
ALARM GENERATION REGISTER (AGR)(ADDRESS = 0XN108H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
REV. 1.2.0
3-2
Transmit AIS Select
R/W
These READ/WRITE bit-fields allows the user to choose which one of the two AIS pattern supported by the XRT86VL3x framer will be transmitted. 00 - No AIS alarm is generated. 01 - Enable unframed AIS alarm of all ones pattern. 10 - Enable framed AIS alarm of all ones pattern except for framing bits. 11 - No AIS alarm is generated.
8.6.2
How to configure the framer to generate Red Alarm
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the Repeater will generate an internal Red Alarm when enabled. This alarm will normally trigger a microprocessor interrupt informing the user that an incoming signal failure is happening. The Loss of Frame Declaration Enable bit of the Alarm Generation Register (AGR) enables the generation of Red Alarm. The table below shows configurations of the of Frame Declaration Enable bit of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR)(ADDRESS = 0XN108H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
6
Loss of Frame Declaration Enable
R/W
This READ/WRITE bit-field permits the framer to declare Red Alarm in case of Loss of Frame Alignment (LOF). When receiver module of the framer detects Loss of Frame Alignment in the incoming data stream, it will generate a Red Alarm. The framer will also generate an RxLOFs interrupt to notify the microprocessor that an LOF condition is occurred. A Yellow Alarm is then returned to the remote transmitter to report that the local receiver detects LOF. 0 - Red Alarm declaration is disabled. 1 - Red Alarm declaration is enabled.
8.6.3
How to configure the framer to transmit Yellow Alarm
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the receiver will transmit the Yellow Alarm back to the source indicating the loss of an incoming signal. This Yellow Alarm informs the source that there is a problem further down the line and its transmission is not being received at the destination. The XRT86VL3x framer supports transmission of Yellow Alarm when running at the following framing formats:
* SF Mode * ESF Mode * N Mode * T1DM Mode
Yellow alarm is transmitted in different forms for various framing formats. The Yellow Alarm Generation Select bits of the Alarm Generation Register (AGR) enable transmission of different types of Yellow alarm that are supported by the XRT86VL3x framer.
105
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION Transmit Yellow Alarm in SF Mode
8.6.4
In SF mode, the XRT86VL3x supports transmission of Yellow Alarm in two ways. When the Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 01 or 11, the second MSB of all DS0 channels is transmitted as zero. This is Yellow Alarm for DS1 standard. When the Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 10, the Framing bit of Frame 12 is transmitted as one. This is Yellow Alarm for J1 standard. 8.6.5 Transmit Yellow Alarm in ESF Mode
In ESF mode, the XRT86VL3x transmits Yellow Alarm on the 4Kbit/s data link channel. The Facility Data Link bits are sent in the pattern of eight ones followed by eight zeros. The number of repetitions of this pattern depends on the duration of Yellow Alarm Generation Select bits of the Alarm Generation Register. When these select bits are set to 01 or 11, the following scenario will happen: 1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width shorter or equal to the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm is transmitted for 255 patterns. 2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width longer than the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm continues until Bit 0 goes LOW. 3. A second pulse on Bit 0 of Yellow Alarm Generation Select during an alarm transmission resets the pattern counter. The framer will send another 255 patterns of the Yellow Alarm.
NOTE: To pulse Bit 0, this bit must be programmed to "1" and then reset back to "0". The pulse width is the duration in time that this bit remains at "1".
When these select bits are set to 10, Bit 1 of the Yellow Alarm Generation Select forms a pulse that controls the duration of Yellow Alarm transmission. The alarm continues until Bit 1 goes LOW. When these select bits are set to 01, the following scenario will happen: 1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width shorter or equal to the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm is transmitted for 255 patterns. 2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width longer than the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm continues until Bit 0 goes LOW. 3. A second pulse on Bit 0 of Yellow Alarm Generation Select during an alarm transmission resets the pattern counter. The framer will send another 255 patterns of the Yellow Alarm. 8.6.6 Transmit Yellow Alarm in N Mode
In N mode, when the Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 01, 10 or 11, the second MSB of all DS0 channels is transmitted as zero. 8.6.7 Transmit Yellow Alarm in T1DM Mode
In T1DM mode, when the Yellow Alarm Generation Select bits of the Alarm Generation Register are set to 01, 10 or 11, the Yellow Alarm bit (the third LSB of Timeslot 23) is set to zero.The table below shows configurations of the Yellow Alarm Generation Select bits of the Alarm Generation Register (AGR).
106
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
)
REV. 1.2.0
ALARM GENERATION REGISTER (AGR)(ADDRESS = 0XN108H)
BIT NUMBER BIT NAME BIT TYPE BIT DESCRIPTION
5-4
Yellow Alarm Generation Select
R/W
00 - Transmission of Yellow Alarm is disabled. 01 - The framer transmits Yellow Alarm by converting the second MSB of all outgoing twenty-four DS0 channel into zero. 10 - The framer transmits Yellow Alarm by sending the Super-frame Alignment Bit (Fs) of Frame 12 as one. 11 - The framer transmits Yellow Alarm by converting the second MSB of all outgoing twenty-four DS0 channel into zero. N Mode: 00 - Transmission of Yellow Alarm is disabled. 01, 10 or 11 - The framer transmits Yellow Alarm by converting the second MSB of all outgoing twenty-four DS0 channel into zero. ESF Mode: When the framer is in ESF mode, it transmits Yellow Alarm pattern of eight ones followed by eight zeros (1111_1111_0000_0000) through the 4Kbit/s data link bits. 00 - Transmission of Yellow Alarm is disabled. 01 - The following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width
shorter or equal to the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm is transmitted for 255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width
longer than the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm continues until Bit 0 goes LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select during
an alarm transmission resets the pattern counter. The framer will send another 255 patterns of the Yellow Alarm. 10 - Bit 1 of the Yellow Alarm Generation Select forms a pulse that controls the duration of Yellow Alarm transmission. The alarm continues until Bit 1 goes LOW. 11 - The following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width
shorter or equal to the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm is transmitted for 255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width
longer than the time required to transmit 255 patterns on the 4Kbit/s data link, the alarm continues until Bit 0 goes LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select during
an alarm transmission resets the pattern counter. The framer will send another 255 patterns of the Yellow Alarm. T1DM Mode: 00 - Transmission of Yellow Alarm is disabled. 01, 10 or 11 - The framer transmits Yellow Alarm by setting the Yellow Alarm bit (Y-bit) to zero.
107
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
9.0 APPENDIX A: DS-1/E1 FRAMING FORMATS
9.1 The E1 Framing Structure
A single E1 frame consists of 256 bits which is created 8000 times per second. This yields a bit-rate of 2.048Mbps. The 256 bits within each E1 frame are grouped into 32 octets or timeslots. These timeslots are numbered from 0 to 31. Each timeslot is 8 bits in length and is transmitted most significant bit first, numbered bit 0. Figure 99 presents a diagram of a single E1 frame. FIGURE 99. SINGLE E1 FRAME DIAGRAM
E1 Frame
Timeslot 0
Timeslot 1
Timeslot 29
Timeslot 30
Timeslot 31
0
1
2
3
4
5
6
7
Not all of these timeslots are available to transmit voice or user data. For instance, timeslot 0 is always reserved for system use and timeslot 16 is sometimes used (reserved) by the system. Hence, within each E1 frame, either 30 or 31 of the 32 timeslots are available for transporting user or voice data. In general, there are two types of E1 frames, FAS and Non-FAS. In any E1 data stream, the E1 frame begins with a FAS frame followed by NonFAS frame and then alternates between the two. 9.1.1 FAS Frame
Timeslot 0 within the FAS E1 frame contains a framing alignment pattern and therefore supports framing. The bit-format of timeslot 0 is presented in Table 7. The Si bit within the FAS E1 Frame typically carries the results of a CRC-4 calculation. The fixed framing pattern (e.g., 0, 0, 1, 1, 0, 1, 1) will be used by the Receive E1 Framer at the Remote terminal for frame synchronization/alignment purposes. TABLE 7: BIT FORMAT OF TIMESLOT 0 OCTET WITHIN A FAS E1 FRAME
BIT 0 1 2 3 4 5 6 7
Value Function
SI International Bit
0
0
1
1
0
1
1
Frame Alignment Signaling (FAS) Pattern
Description- In practice, the Si bit within the FAS E1 Frame carries the The fixed framing pattern (e.g., 0, 0, 1, 1, 0, 1, 1) Operation results of a CRC-4 calculation, which is discussed in is used by the Receive E1 Framer at the Remote greater detail in Section 9.2.1. terminal for frame synchronization/alignment purposes.
108
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 9.1.2 Non-FAS Frame
REV. 1.2.0
Timeslot 0 within the non-FAS E1 frame contains bits that support signaling or data link message transmission. The bit-format of timeslot 0 is presented in Table 8. The Si bit in the Non-FAS frame typically carries a specific value that will be used by the Receive E1 Framer for CRC Multi-frame alignment purposes. TABLE 8: BIT FORMAT OF TIMESLOT 0 OCTET WITHIN A NON-FAS E1 FRAME
BIT 0 1 2 3 4 5 6 7
Value Function6
Si International Bit
1 Fixed Value Fixed at "1" Bit-field "1" contains a fixed value "1". This bitfield will be used for FAS framing synchronization/alignment purposes by the Remote Receive E1 Framer.
A Yellow Alarm FAS Frame Yellow Alarm Bit This bit-field is used to transmit a Yellow alarm to the Remote Terminal. This bit-field is set to "0" during normal conditions, and is set to "1" whenever the Receive E1 Framer detects an LOS (Loss of Signal) or LOF (Loss of Framing) condition in the incoming E1 frame data.
Sa4 Sa5 Sa6 Sa7 Sa8 National bits National Bits These bit-fields can be used to carry data link information from the Local transmitting terminal to the Remote receiving terminal. Since the National bits only exist in the nonFAS frames, they offer a maximum signaling data link bandwidth of 20kbps.
Description- International Bit Operation The Si bit within the nonFAS E1 Frame typically carries a specific value that will be used by the Receive E1 Framer for CRC Multi-frame alignment purposes.
109
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
9.2
The E1 Multi-frame Structure
There are two types of E1 Multi-frame structures, CRC Multi-frame and CAS Multi-frame. The CAS Multiframe can be considered a subset of the CRC Multi-frame, in that CAS is an option to carry signaling information within the CRC Multi-frame structure. 9.2.1 The CRC Multi-frame Structure
A CRC Multi-frame consists of 16 consecutive E1 frames, with the first of these frames being a FAS frame. From a Frame Alignment point of view, timeslot 0 of each of these E1 frames within the Multi-frame are the most important 16 octets. Table 9 presents the bit-format for all timeslot 0 octets within a 16 frame CRC Multiframe. TABLE 9: BIT FORMAT OF ALL TIMESLOT 0 OCTETS WITHIN A CRC MULTI-FRAME
SMF FRAME NUMBER BIT 0 BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 BIT 7
1
0 1 2 3 4 5 6 7
C1 0 C2 0 C3 1 C4 0 C1 1 C2 1 C3 E C4 E
0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
0 A 0 A 0 A 0 A 0 A 0 A 0 A 0 A
1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4
1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5
0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6
1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7
1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8
2
8 9 10 11 12 13 14 15
The CRC Multi-frame is divided into 2 sub Multi-Frames. Sub-Multi-Frame 1 is designated as SMF1 and SubMulti-Frame 2 is designated as SMF2. SMF1 and SMF2 each consist of 8 E1 frames having 4 FAS frames and 4 non-FAS frames. There are two interesting things to note in Table 9. First, all of the bit-field 0 positions within each of the FAS frames (within each SMF) are designated as C1, C2, C3 and C4. These four bit-fields contain the CRC-4 values which have been computed over the previous SMF. Hence, while the Transmit E1 Framer is assembling a given SMF, it computes the CRC-4 value for that SMF and inserts these results into the C1 through C4 bit-fields within the very next SMF. These CRC-4 values ultimately are used by the Remote Receive E1 Framer for error detection purposes.
NOTE: This framing structure is referred to as a CRC Multi-Frame because it permits the remote receiving terminal to locate and verify the CRC-4 bit-fields.
The second interesting thing to note regarding Table 9 is that the bit-field 0 positions within each of the nonFAS frames (within the entire MF) are of a fixed 6-bit pattern 0, 0, 1, 0, 1, 1 along with two bits, each designated as "E". This 6-bit pattern is referred to as the CRC Multi-Frame alignment pattern, which can ultimately be used by the Remote Receive E1 Framer for CRC Multi-Frame synchronization/alignment. The "E" bits are used to indicate that the Local Receive E1 framer has detected errored sub-Multi-Frames.
110
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION 9.2.2 CAS Multi-Frames and Channel Associated Signaling
REV. 1.2.0
CAS Multi-Frames are only relevant if the user is using CAS or Channel Associated Signaling. If the user is implementing Common Channel Signaling then the CAS Multi-Frame is not available.
9.2.2.1 Channel Associated Signaling
If the user operates an E1 channel in Channel Associated Signaling, then timeslot 16 octets within each E1 frame will be reserved for signaling. Such signaling would convey information such as On-Hook, Off-Hook conditions, call set-up, control, etc. In CAS, this type of signaling data that is associated with a particular voice channel will be carried within timeslot 16 of a particular E1 frame within a CAS Multi-Frame. The CAS is carried in a Multi-Frame structure which consists of 16 consecutive E1 frames. The framing/byte format of a CAS Multi-Frame is presented in Figure 100. FIGURE 100. FRAME/BYTE FORMAT OF THE CAS MULTI-FRAME STRUCTURE
A Single CAS Multiframe
Timeslot 16 Frame 0 Timeslot 16 Frame 1 Timeslot 16 Frame 2 Timeslot 16 Frame 15
0000
xyxx
ABCD
ABCD
ABCD
ABCD
ABCD ABCD
CAS Multiframe Alignment Pattern
Signaling Data Associated with Timeslot 1
Signaling Data Associated with Timeslot 2 Signaling Data Associated with Timeslot 18
Signaling Data Associated with Timeslot 15 Signaling Data Associated with Timeslot 31
Signaling Data Associated with Timeslot 17
x = "dummy bits" y = Carries the Multiframe "Yellow Alarm" bit
Timeslot 16 within frame 0 is a special octet that is used to convey CAS Multi-Frame alignment information, and to convey Multi-Frame alarm information to the Remote Terminal. The bit-format of timeslot 16 within frame 0 of a CAS Multi-Frame is 0000 xyxx. The upper nibble of this octet contains all zeros and is used to identify itself as the CAS Multi-Frame alignment signal. If CAS is used, then the user is advised to insure that none of the other timeslot 16 octets contain the value "0000". The lower nibble of this octet contains the expression "xyxx". The x-bits are the spare bits and should be set to "0" if not used. The y-bit is used to indicate a Multi-Frame alarm condition to the Remote terminal. During normal operation, this bit-field is cleared to "0". However, if the Local Receive E1 Framer detects a problem with the incoming Multi-Frames, then the Local Transmit E1 Framer will set this bit-field within the next outbound CAS Multi-Frame to "1".
NOTE: The Local Transmit E1 Framer will continue to set the y-bit to "1" for the duration that the Local Receive E1 Framer detects this problem.
Timeslot 16 within Frame 1 of the CAS Multi-Frame contains 4 bits of signaling data for voice channel 1 and 4 bits of signaling data for voice channel 17. Timeslot 16 within Frame 2 contains 4 bits of signaling data for voice channel 2 and 4 bits of signaling data for voice channel 18, and this continues for all E1 frames.
111
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
Common Channel Signaling (CCS)
9.2.2.2
Common Channel Signaling is an alternative form of signaling from CAS. In CCS, whatever signaling data which is transported via the outbound E1 data stream, carries information that applies to all of the voice channels as a set (e.g., timeslots 1 through 15 and 17 through 31) in the E1 frame. There are numerous other variations of Common Channel Signaling that are available. Some of these are listed below.
* 31 Voice Channels with the common channel signaling being transported via the National Bits. * 30 Voice Channels with the common channel signaling data being transported via the National Bits and CAS
data being transported via timeslot 16.
* 30 Voice Channels with the Common Channel Signaling being processed via timeslot 16. (e.g., Primary Rate
ISDN Signaling). FIGURE 101. E1 FRAME FORMAT
Time Slot 0 Time Slot 16 Time Slots 1-15, 17-31
a. Even Frames 0, 2, 4-14 1 0 0 1 1 0 1 1
a. Frame 0 0 0 0 0 X Y X X Channel Data
FAS b. Odd Frames 1, 3, 5-15 8 Bits/ Time Slot 1 1 A N N N N N
CAS b. Frames 1-15 A B C D A B C D 0 1 2 3 4 5 6 7
Non-FAS
32 Time Slots/Frame
TS 0
TS 1
TS 2
TS 3 - 14
TS 15
TS 16
TS 17
TS 18 - 28
TS 29
TS 30
TS 31
16 Frames/ Multiframe
FR 0
FR 1
FR 2
FR 3
FR 4
FR 5
FR 6
FR 7
FR 8
FR 9
FR 10
FR 11
FR 12
FR 13
FR 14
FR 15
112
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
9.3 The DS1 Framing Structure
REV. 1.2.0
A single T1 frame is 193 bits long and is transmitted at a frame rate of 8000Hz. This results in an aggregate bit rate of 1.544 Mbit/s. Basic frames are divided into 24 timeslots numbered 1 thru 24 and a framing bit as shown in Figure 102. Each timeslot is 8 bits in length and is transmitted most significant bit first, numbered bit 0. This results in a single timeslot data rate of 8 bits x 8000/sec = 64 kbit/s. FIGURE 102. T1 FRAME FORMAT
DS1 Frame 125s Timeslot 1 Timeslot 2 - 23 Timeslot 23 Timeslot 24
F-bit
0Bit 0
1Bit 1
2Bit 2
3Bit 3
4Bit 4
5Bit 5
6Bit 6
7Bit 7
113
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
9.4
T1 Super Frame Format (SF)
The Superframe Format (SF), is also referred to as the D4 format. The requirement for associated signaling in frames 6 and 12 dictates that the frames be distinguishable. This leads to a multiframe structure consisting of 12 frames per superframe (SF) as shown in Figure 103 and Table 10. This structure of frames and multiframes is defined by the F-bit pattern. The F-bit is designated alternately as an Ft bit (terminal framing bit) or Fs bit (signalling framing bit). The Ft bit carries a pattern of alternating zeros and ones (101010) in odd frames that defines the boundaries so that one timeslot may be distinguished from another. The Fs bit carries a pattern of (001110) in even frames and defines the multiframe boundaries so that one frame may be distinguished from another. FIGURE 103. T1 SUPERFRAME PCM FORMAT
SignallingInformation B 8 Bits per Timeslot A Bit 7 During: Frame 12 Frame 6
Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
Ft TS TS TS TS or Ft -----------------TS ------------------TS 1 TS 2 TS 13 ------------------------------------ 24 Fs or 13 24 1 2 Fs
24 Timeslots per Frame Frame = 193 Bits
FR FR FR FR FR -----------------------------------FR FR 12 1 FR 2 FR 7 FR 11 -----------------------------------1 2 12 7 11
Multiframe SF = 12 Frames
TABLE 10: SUPERFRAME FORMAT
F-BITS FRAME BIT TERMINAL FRAMING FT TERMINAL FRAMING FS BIT USE IN EACH TIMESLOT TRAFFIC SIG SIGNALLING CHANNEL
1 2 3 4 5 6 7 8
0 193 386 579 772 965 1158 1351
1 ---0 ---1 ---0 ----
---0 ---0 ---1 ---1
1-8 1-8 1-8 1-8 1-8 1-7 1-8 1-8
---------------8 -------
---------------A -------
114
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION TABLE 10: SUPERFRAME FORMAT
F-BITS FRAME BIT TERMINAL FRAMING FT TERMINAL FRAMING FS BIT USE IN EACH TIMESLOT TRAFFIC SIG SIGNALLING CHANNEL
REV. 1.2.0
9 10 11 12
1544 1737 1930 2123
1 ---0 ----
---1 ---0
1-8 1-8 1-8 1-7
---------8
---------B
9.5
T1 Extended Superframe Format (ESF)
In Extended Superframe Format (ESF), as shown in Figure 104 and Table 11, the multiframe structure is extended to 24 frames. The timeslot structure is identical to D4 (SF) format. Robbed-bit signaling is accommodated in frame 6 (A-bit), frame 12 (B-bit), frame 18 (C-bit) and frame 24 (D-bit). The F-bit pattern of ESF contains three functions: 1. Framing Pattern Sequence (FPS), which defines the frame and multiframe boundaries. 2. Facility Data Link (FDL), which allows data such as error-performance to be passed within the T1 link. 3. Cyclic Redundancy Check (CRC), which allows error performance to be monitored and enhances the reliability of the receiver's framing algorithm. FIGURE 104. T1 EXTENDED SUPERFRAME FORMAT
Signalling Information D C B A Bit 5 Bit 6 Bit 7 Bit 7 During: Frame 24 Frame 18 Frame 12 Frame 6
Bit 0
Bit 1
8 Bits per Timeslot Bit Bit Bit 2 3 4
CRC FD CRC L FD FPS L FP TS TS ----------------or ----------------o S 1 TS 2 TS Fs F r 2 1 s
TS -----------------TS -----------------13 13 -
TS TS 24 24
24 Timeslots per Frame Frame = 193 Bits
FR FR --------------------------------1 FR 2 FR 1 2 -
FR -----------------FR -----------------13 13 -
FR FR FR 24 FR 23 23 24
Multiframe ESF = 24 Frames
115
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION TABLE 11: EXTENDED SUPERFRAME FORMAT
F-BITS BIT USE IN EACH TIMESLOT CRC TRAFFIC SIG SIGNALLING CHANNEL 16 4 2
FRAME
BIT FPS DL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
NOTES: 1. 2. 3. 4.
0 193 386 579 772 965 1158 1351 1544 1737 1930 2123 2316 2509 2702 2895 3088 3281 3474 3667 3860 4053 4246 4439
---------0 ---------0 ---------1 ---------0 ---------1 ---------1
m ---m ---m ---m ---m ---m ---m ---m ---m ---m ---m ---m ----
---C1 ---------C2 ---------C3 ---------C4 ---------C5 ---------C6 -------
1-8 1-8 1-8 1-8 1-8 1-7 1-8 1-8 1-8 1-8 1-8 1-7 1-8 1-8 1-8 1-8 1-8 1-7 1-8 1-8 1-8 1-8 1-8 1-7
---------------8 ---------------8 ---------------8 ---------------8
---------------A ---------------B ---------------C ---------------D
---------------A ---------------B ---------------A ---------------B
---------------A ---------------A ---------------A ---------------A
FPS indicates the Framing Pattern Sequence (...001011...) DL indicates the 4kb/s Data Link with message bits m. CRC indicates the cyclic redundancy check with bits C1 to C6 Signaling options include 16 state, 4 state and 2 state.
116
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
9.6 T1 Non-Signaling Frame Format
REV. 1.2.0
The Non-Signaling (N) framing format is a simplified version of the T1 super frame. The N-Frame consists of four frames with two Fs bits and two Ft bits. The Fs bits can be used as a proprietary 4kbps data link transmission. Signaling is not supported in this framing format. TABLE 12: NON-SIGNALING FRAMING FORMAT
F-BITS FRAME BIT TERMINAL FRAMING FT TERMINAL FRAMING FS
1 2 3 4
0 193 386 579
1 ---0 ----
---X ---X
9.7
T1 Data Multiplexed Framing Format (T1DM)
T1DM uses a similar framing structure as the SF (D4), such that the Fs and Ft bits on the individual frame boundaries remain the same. The differentiation between T1DM and SF is within the payload time slots. Time slot 24 cannot be used for data when configured for T1DM. Time slot 24 is dedicated for a special synchronization byte as shown in Figure 105. The Y-bit is to carry the status of the Yellow Alarm. The R-bit is dedicated for a remote signaling bit typically not used. However, the framer allows this bit to carry an HDLC message. Time slots 1 through 23 are used to carry the seven bit word from each of the 23 DS-0 signals. FIGURE 105. T1DM FRAME FORMAT
T1DM Frame
12 T1DM Frames per Multi-frame
F
Time Slot 1
Time Slots 2 through 23
Time Slot 24
Bit 1 Bit 2
Bit 3 Bit 4 Bit 5
Bit 6 Bit 7
C
1
0
1
1
1
Y
R
0
117
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
9.8
SLC-96 Format (SLC-96)
SLC framing mode allows synchronization to the SLC(R)96 data link pattern. This pattern described in Bellcore TR-TSY-000008, contains both signaling information and a framing pattern that overwrites the Fs bit of the SF framer pattern. See Table 13. TABLE 13: SLC(R)96 FS BIT CONTENTS
FRAME # FS BIT FRAME # FS BIT FRAME # FS BIT
2 4 6 8 10 12 14 16 18 20 22 24
NOTES: 1. 2. 3. 4. 5. 6.
0 0 1 1 1 0 0 0 1 1 1 C1
26 28 30 32 34 36 38 40 42 44 46 48
C2 C3 C4 C5 C6 C7 C8 C9 C10 C11 0 1
50 52 54 56 58 60 62 64 66 68 70 72
0 M1 M2 M3 A1 A2 S1 S2 S3 S4 1 0
The SLC(R)96 frame format is similar to that of SF as shown in Table 10 with the exceptions shown in this table. C1 to C11 are concentrator bit fields. M1 to M3 are Maintenance bit fields. A1 and A2 are alarm bit fields. S1 to S4 are line switch bit fields. The Fs bits in frames 46, 48 and 70 are spoiler bit switch are used to protect against false multiframing.
118
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
ELECTRICAL CHARACTERISTICS ABSOLUTE MAXIMUMS
REV. 1.2.0
Power Supply..................................................................... VDDIO .. ................................................ -0.5V to +3.465V VDDCORE...............................................-0.5V to +1.890V
Power Rating PBGA Package..................................1.39W (XRT86VL32/VL34) Power Rating STBGA and PBGA Package ...............2.4W (XRT86VL38)
Storage Temperature ...............................-65C to 150C Operating Temperature Range.................-40C to 85C Supply Voltage ...................... GND-0.5V to +VDD + 0.5V
Input Logic Signal Voltage (Any Pin) .........-0.5V to + 5.5V ESD Protection (HBM)...........................................>2000V Input Current (Any Pin) ...................................... + 100mA
DC ELECTRICAL CHARACTERISTICS
Test Conditions: TA = 25C, VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5% unless otherwise specified SYMBOL PARAMETER MIN. TYP. MAX. UNITS CONDITIONS
ILL VIL VIH VOL VOH IOC IIH IIL
Data Bus Tri-State Bus Leakage Current Input Low voltage Input High Voltage Output Low Voltage Output High Voltage Open Drain Output Leakage Current Input High Voltage Current Input Low Voltage Current
-10
+10 0.8
A V V V V A IOL = -1.6mA IOH = 40A
2.0 0.0 2.4
VDD 0.4 VDD
-10 -10
10 10
A A
VIH = VDD VIL = GND
TABLE 14: XRT86VL32 POWER CONSUMPTION
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5% , TA=25C, UNLESS OTHERWISE SPECIFIED MODE SUPPLY VOLTAGE IMPEDANCE
TERMINATION
TRANSFORMER RATIO TYP. RECEIVER TRANSMITTER MAX. UNIT
RESISTOR
TEST CONDITIONS
E1
3.3V
75
Internal
1:1
1:2
776
mW
PRBS Pattern
E1
3.3V
120
Internal
1:1
1:2
724
mW
PRBS Pattern
T1
3.3V
100
Internal
1:1
1:2
829
mW
PRBS Pattern
119
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION TABLE 15: XRT86VL34 POWER CONSUMPTION
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5% , TA=25C, UNLESS OTHERWISE SPECIFIED
MODE
SUPPLY VOLTAGE
IMPEDANCE
TERMINATION
TRANSFORMER RATIO TYP. RECEIVER TRANSMITTER MAX. UNIT
RESISTOR
TEST CONDITIONS
E1
3.3V
75
Internal
1:1
1:2
1.035
W
PRBS Pattern
E1
3.3V
120
Internal
1:1
1:2
0.965
W
PRBS Pattern
T1
3.3V
100
Internal
1:1
1:2
1.105
W
PRBS Pattern
TABLE 16: XRT86VL38 POWER CONSUMPTION
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5% , TA=25C, UNLESS OTHERWISE SPECIFIED MODE SUPPLY VOLTAGE IMPEDANCE
TERMINATION
TRANSFORMER RATIO TYP. RECEIVER TRANSMITTER MAX. UNIT
RESISTOR
TEST CONDITIONS
E1
3.3V
75
Internal
1:1
1:2
2.070
W
PRBS Pattern
E1
3.3V
120
Internal
1:1
1:2
1.930
W
PRBS Pattern
T1
3.3V
100
Internal
1:1
1:2
2.210
W
PRBS Pattern
120
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
AC ELECTRICAL CHARACTERISTICS TRANSMIT FRAMER (BASE RATE/NON-MUX)
Test Conditions: TA = 25C, VDD = 3.3V + 5% unless otherwise specified SYMBOL t1 t2 t3 t4 t5 t6 t7 PARAMETER MIN. TYP. MAX. UNITS CONDITIONS
TxSERCLK to TxMSYNC delay TxSERCLK to TxSYNC delay TxSERCLK to TxSER data delay Rising Edge of TxSERCLK to Rising Edge of TxCHCLK Rising Edge of TxCHCLK to Valid TxCHN[4:0] Data TxSERCLK to TxSIG delay TxSERCLK to TxFRACT delay
234 230 230 13 6 230 110
nS nS nS nS nS nS nS
FIGURE 106. FRAMER SYSTEM TRANSMIT TIMING DIAGRAM (BASE RATE/NON-MUX)
t1
TxMSYNC
t2
TxSYNC
TxSERCLK
t3
TxSER
TxCHCLK (Output) TxCHN[4:0] (Output) TxCHN_0 (TxSIG) TxCHN_1 (TxFRACT)
t4 t5 t6
A B C D
t7
121
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
AC ELECTRICAL CHARACTERISTICS RECEIVE FRAMER (BASE RATE/NON-MUX)
Test Conditions: TA = 25C, VDD = 3.3V + 5% unless otherwise specified SYMBOL RxSERCLK as an Output t8 t9 t10 t11 t12 PARAMETER MIN. TYP. MAX. UNITS CONDITIONS
Rising Edge of RxSERCLK to Rising Edge of RxCASYNC Rising Edge of RxSERCLK to Rising Edge of RxCRCSYNC Rising Edge of RxSERCLK to Rising Edge of RxSYNC (RxSYNC as Output) Rising Edge of RxSERCLK to Rising Edge of RxSER Rising Edge of RxSERCLK to Rising Edge of Valid RxCHN[4:0] data
4 4 4 6 6
nS nS nS nS nS
RxSERCLK as an Input t13 t14 t15 t15 t16 t17
Rising Edge of RxSERCLK to Rising Edge of RxCASYNC Rising Edge of RxSERCLK to Rising Edge of RxCRCSYNC Rising Edge of RxSERCLK to Rising Edge of RxSYNC (RxSYNC as Output) Rising Edge of RxSERCLK to Rising Edge of RxSYNC (RxSYNC as Input) Rising Edge of RxSERCLK to Rising Edge of RxSER Rising Edge of RxSERCLK to Rising Edge of Valid RxCHN[4:0] data
8 8 10 230 10 9
nS nS nS nS nS nS
FIGURE 107. FRAMER SYSTEM RECEIVE TIMING DIAGRAM (RXSERCLK AS AN OUTPUT)
t8
RxCRCSYNC
t9
RxCASYNC
t10
RxSYNC RxSERCLK (Output)
t11
RxSER
t12
RxCHN[4:0]
122
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 108. FRAMER SYSTEM RECEIVE TIMING DIAGRAM (RXSERCLK AS AN INPUT)
t13
RxCRCSYNC
REV. 1.2.0
t14
RxCASYNC
t15
RxSYNC RxSERCLK (Input)
t16
RxSER
t17
RxCHN[4:0]
123
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
AC ELECTRICAL CHARACTERISTICS TRANSMIT FRAMER (HMVIP/H100 MODE)
Test Conditions: TA = 25C, VDD = 3.3V + 5% unless otherwise specified SYMBOL t1 t2 t3 t4 t5 t6 t7 t8 PARAMETER MIN. TYP. MAX. UNITS CONDITIONS
TxSYNC Setup Time - HMVIP Mode TxSYNC Hold Time - HMVIP Mode TxSYNC Setup Time - H100 Mode TxSYNC Hold Time - H100 Mode TxSER Setup Time - HMVIP and H100 Mode TxSER Hold Time - HMVIP and H100 Mode TxSIG Setup Time - HMVIP and H100 Mode TxSIG Hold Time - HMVIP and H100 Mode
7 4 7 4 6 3 6 3
nS nS nS nS nS nS nS nS
FIGURE 109. FRAMER SYSTEM TRANSMIT TIMING DIAGRAM (HMVIP AND H100 MODE)
TxInClk (16MHz) TxSYNC (HMVIP Mode)
t1 t4 t3
t2
TxSYNC (H100 Mode)
TxSERCLK
TxSER
t5 t6 t8 t7
A B C D
TxCHN_0 (TxSIG)
NOTE: Setup and Hold time is not valid from TxInClk to TxSERCLK as TxInClk is used as the timing source for the back plane interface and TxSERCLK is used as the timing source on the line side.
124
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
AC ELECTRICAL CHARACTERISTICS RECEIVE FRAMER (HMVIP/H100 MODE)
Test Conditions: TA = 25C, VDD = 3.3V + 5% unless otherwise specified SYMBOL t1 t2 t3 t4 t5 PARAMETER MIN. TYP. MAX. UNITS CONDITIONS
RxSYNC Setup Time - HMVIP Mode RxSYNC Hold Time - HMVIP Mode RxSYNC Setup Time - H100 Mode RxSYNC Hold Time - H100 Mode Rising Edge of RxSERCLK to Rising Edge of RxSER delay
4 3 5 3 11
nS nS nS nS nS
NOTE: Both RxSERCLK and RxSYNC are inputs
FIGURE 110. FRAMER SYSTEM RECEIVE TIMING DIAGRAM (HMVIP/H100 MODE)
RxSERCLK (16MHz) RxSYNC (HMVIP Mode)
t1 t4 t3
t2
RxSYNC (H100 Mode)
RxSER
t5
125
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
AC ELECTRICAL CHARACTERISTICS TRANSMIT OVERHEAD FRAMER
Test Conditions: TA = 25C, VDD = 3.3V + 5% unless otherwise specified SYMBOL t18 t19 t20 PARAMETER MIN. TYP. MAX. UNITS CONDITIONS
TxSYNC Setup Time (Falling Edge TxSERCLK) TxSYNC Hold Time (Falling Edge TxSERCLK) Rising Edge of TxSERCLK to TxOHCLK
6 4 12
nS nS nS
FIGURE 111. FRAMER SYSTEM TRANSMIT OVERHEAD TIMING DIAGRAM
t18 TxSYNC
t19
TxSERCLK t20 TxOHCLK
126
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
AC ELECTRICAL CHARACTERISTICS RECEIVE OVERHEAD FRAMER
Test Conditions: TA = 25C, VDD = 3.3V + 5% unless otherwise specified SYMBOL RxSERCLK as an Output t21 t22 t23 PARAMETER MIN. TYP. MAX. UNITS CONDITIONS
Rising Edge of RxSERCLK to Rising Edge of RxSYNC (RxSYNC as Output) Rising Edge of RxSERCLK to Rising Edge of RxOHCLK Rising Edge of RxSERCLK to Rising Edge of RxOH
4 6 8
nS nS nS
RxSERCLK as an Input t24 t24 t25 t26
Rising Edge of RxSERCLK to Rising Edge of RxSYNC (RxSYNC as Output) Rising Edge of RxSERCLK to Rising Edge of RxSYNC (RxSYNC as Input) Rising Edge of RxSERCLK to Rising Edge of RxOHCLK Rising Edge of RxSERCLK to Rising Edge of RxOH
12 230 12 15
nS nS nS nS
FIGURE 112. FRAMER SYSTEM RECEIVE OVERHEAD TIMING DIAGRAM (RXSERCLK AS AN OUTPUT)
t21
RxSYNC RxSERCLK (Output)
t22
RxOHCLK
t23
RxOH
FIGURE 113. FRAMER SYSTEM RECEIVE OVERHEAD TIMING DIAGRAM (RXSERCLK AS AN INPUT)
RxOH Interface with RxSERCLK as an Input
t24
RxSYNC RxSERCLK (Input)
t25 t26
RxOHCLK RxOH
127
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
TABLE 17: E1 RECEIVER ELECTRICAL CHARACTERISTICS
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5%, TA= -40 to 85C, unless otherwise specified PARAMETER MIN. TYP. MAX. UNIT TEST CONDITIONS
Receiver loss of signal: Number of consecutive zeros before RLOS is set Input signal level at RLOS RLOS De-asserted Receiver Sensitivity (Short Haul with cable loss) 15 12.5 11
Cable attenuation @1024kHz
32 20 dB % ones dB With nominal pulse amplitude of 3.0V for 120 and 2.37V for 75 application. With -18dB interference signal added. With nominal pulse amplitude of 3.0V for 120 and 2.37V for 75 application. With -18dB interference signal added. ITU-G.775, ETSI 300 233
Receiver Sensitivity (Long Haul with cable loss)
0
43
dB
Input Impedance
Input Jitter Tolerance: 1 Hz 10kHz-100kHz
13
k
37 0.2
UIpp UIpp
ITU G.823
Recovered Clock Jitter Transfer Corner Frequency Peaking Amplitude
Jitter Attenuator Corner Frequency (-3dB curve) (JABW=0) (JABW=1) Return Loss: 51kHz - 102kHz 102kHz - 2048kHz 2048kHz - 3072kHz
-
36 -0.5
kHz dB
ITU G.736
-
10 1.5
-
Hz Hz
ITU G.736
14 20 16
-
-
dB dB dB
ITU-G.703
128
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION TABLE 18: T1 RECEIVER ELECTRICAL CHARACTERISTICS
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5%, TA=-40 to 85C, unless otherwise specified PARAMETER MIN. TYP. MAX. UNIT TEST CONDITIONS
REV. 1.2.0
Receiver loss of signal: Number of consecutive zeros before RLOS is set Input signal level at RLOS RLOS Clear Receiver Sensitivity (Short Haul with cable loss) Receiver Sensitivity (Long Haul with cable loss) Normal Extended Input Impedance Jitter Tolerance: 1Hz 10kHz - 100kHz Recovered Clock Jitter Transfer Corner Frequency Peaking Amplitude Jitter Attenuator Corner Frequency (-3dB curve) Return Loss: 51kHz - 102kHz 102kHz - 2048kHz 2048kHz - 3072kHz 160 175 190
15 12.5 12
20 -
-
dB % ones dB
Cable attenuation @772kHz ITU-G.775, ETSI 300 233 With nominal pulse amplitude of 3.0V for 100 termination
0 0 13 36 45 dB dB k With nominal pulse amplitude of 3.0V for 100 termination
138 0.4
-
-
UIpp
AT&T Pub 62411
-
9.8
0.1
KHz dB -Hz
TR-TSY-000499
6
AT&T Pub 62411
-
20 25 25
-
dB dB dB
TABLE 19: E1 TRANSMIT RETURN LOSS REQUIREMENT
RETURN LOSS FREQUENCY G.703/CH-PTT ETS 300166
51-102kHz 102-2048kHz 2048-3072kHz
8dB 14dB 10dB
6dB 8dB 8dB
129
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION TABLE 20: E1 TRANSMITTER ELECTRICAL CHARACTERISTICS
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5%, TA=-40 to 85C, unless otherwise specified PARAMETER MIN. TYP. MAX. UNIT TEST CONDITIONS
AMI Output Pulse Amplitude: 75 Application 120 Application Output Pulse Width Output Pulse Width Ratio Output Pulse Amplitude Ratio Jitter Added by the Transmitter Output Output Return Loss: 51kHz -102kHz 102kHz-2048kHz 2048kHz-3072kHz 2.13 2.70 224 0.95 0.95 2.37 3.00 244 0.025 2.60 3.30 264 1.05 1.05 0.05 V V ns UIpp
Transformer with 1:2 ratio and 9.1 resistor in series with each end of primary.
ITU-G.703 ITU-G.703 Broad Band with jitter free TCLK applied to the input.
8 14 10
-
-
dB dB dB
ETSI 300 166, CHPTT
TABLE 21: T1 TRANSMITTER ELECTRICAL CHARACTERISTICS
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5%, TA=-40 to 85C, unless otherwise specified PARAMETER MIN. TYP. MAX. UNIT TEST CONDITIONS
AMI Output Pulse Amplitude:
2.4
3.0
3.60
V
Use transformer with 1:2.45 ratio for external termination, and transformer with 1:2 ratio for internal termination, and measured at DSX-1 ANSI T1.102 ANSI T1.102 ANSI T1.102 Broad Band with jitter free TCLK applied to the input.
Output Pulse Width Output Pulse Width Imbalance Output Pulse Amplitude Imbalance Jitter Added by the Transmitter Output Output Return Loss: 51kHz -102kHz 102kHz-2048kHz 2048kHz-3072kHz
338 -
350 0.025
362 20 +200 0.05
ns mV UIpp
-
15 15 15
-
dB dB dB
130
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION FIGURE 114. ITU G.703 PULSE TEMPLATE
269 ns (244 + 25)
20%
REV. 1.2.0
10%
V = 100%
10%
20%
194 ns (244 - 50)
Nominal pulse
50%
244 ns
10%
488 ns (244 + 244) Note - V corresponds to the nominal peak value.
TABLE 22: TRANSMIT PULSE MASK SPECIFICATION
Test Load Impedance Nominal Peak Voltage of a Mark Peak voltage of a Space (no Mark) Nominal Pulse width Ratio of Positive and Negative Pulses Imbalance 75 Resistive (Coax) 2.37V 0 + 0.237V 244ns 0.95 to 1.05 120 Resistive (twisted Pair) 3.0V 0 + 0.3V 244ns 0.95 to 1.05
20%
131
10%
0%
10%
10%
219 ns (244 - 25)
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
FIGURE 115. DSX-1 PULSE TEMPLATE (NORMALIZED AMPLITUDE)
TABLE 23: DSX1 INTERFACE ISOLATED PULSE MASK AND CORNER POINTS
MINIMUM CURVE TIME (UI) NORMALIZED AMPLITUDE TIME (UI) MAXIMUM CURVE NORMALIZED AMPLITUDE
-0.77 -0.23 -0.23 -0.15 0.0 0.15 0.23 0.23 0.46 0.66 0.93 1.16
-.05V -.05V 0.5V 0.95V 0.95V 0.9V 0.5V -0.45V -0.45V -0.2V -0.05V -0.05V
-0.77 -0.39 -0.27 -0.27 -0.12 0.0 0.27 0.35 0.93 1.16
.05V .05V .8V 1.15V 1.15V 1.05V 1.05V -0.07V 0.05V 0.05V
132
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION TABLE 24: AC ELECTRICAL CHARACTERISTICS
VDDIO = 3.3V + 5% , VDDCORE = 1.8V + 5%, TA=25C, UNLESS OTHERWISE SPECIFIED PARAMETER SYMBOL MIN. TYP. MAX. UNITS
REV. 1.2.0
MCLKIN Clock Duty Cycle MCLKIN Clock Tolerance
40 -
50
60 -
% ppm
133
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
MICROPROCESSOR INTERFACE I/O TIMING
INTEL INTERFACE TIMING - ASYNCHRONOUS The signals used for the Intel microprocessor interface are: Address Latch Enable (ALE), Read Enable (RD), Write Enable (WR), Chip Select (CS), Address and Data bits. The microprocessor interface uses minimum external glue logic and is compatible with the timings of the 8051 or 80188 family of microprocessors. The ALE signal can be tied 'HIGH' if this signal is not available, and the corresponding timing interface is shown in Figure 117 and Table 26. FIGURE 116. INTEL P INTERFACE TIMING DURING PROGRAMMED I/O READ AND WRITE OPERATIONS WHEN ALE IS NOT TIED 'HIGH'
t5
READ OPERATION
t0 Valid Address
t5
WRITE OPERATION
ALE
t0
ADDR [14:0]
Valid Address
CS
DATA[7:0] t1 RD
Valid Data for Readback
Data Available to Write Into the LIU
t3 WR t2 t4 RDY
TABLE 25: INTEL MICROPROCESSOR INTERFACE TIMING SPECIFICATIONS
SYMBOL PARAMETER MIN MAX UNITS
t0 t1 t2 NA t3 t4 NA t5
Valid Address to CS Falling Edge and ALE Rising Edge ALE Falling Edge to RD Assert RD Assert to RDY Assert RD Pulse Width (t2) ALE Falling Edge to WR Assert WR Assert to RDY Assert WR Pulse Width (t4) ALE Pulse Width(t5)
0 5 140 5 140 10
140 140 -
ns ns ns ns ns ns ns ns
134
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REV. 1.2.0
FIGURE 117. INTEL P INTERFACE TIMING DURING PROGRAMMED I/O READ AND WRITE OPERATIONS WHEN ALE IS TIED 'HIGH'
READ OPERATION
ALE t0 Valid Address t0
WRITE OPERATION
ADDR[14:0]
Valid Address
CS
DATA[7:0] t1 RD
Valid Data for Readback
Data Available to Write Into the LIU
t3 WR t2 t4 RDY
TABLE 26: INTEL MICROPROCESSOR INTERFACE TIMING SPECIFICATIONS
SYMBOL PARAMETER MIN MAX UNITS
t0 t1 t2 NA t3 t4 NA
Valid Address to CS Falling Edge CS Falling Edge to RD Assert RD Assert to RDY Assert RD Pulse Width (t2) CS Falling Edge to WR Assert WR Assert to RDY Assert WR Pulse Width (t4)
0 0 140 0 140
140 140 -
ns ns ns ns ns ns ns
135
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
MOTOROLA ASYCHRONOUS INTERFACE TIMING The signals used in the Motorola microprocessor interface mode are: Address Strobe (AS), Data Strobe (DS), Read/Write Enable (R/W), Chip Select (CS), Address and Data bits. The interface is compatible with the timing of a Motorola 68000 microprocessor family. The interface timing is shown in Figure 118. The I/O specifications are shown in Table 27. FIGURE 118. MOTOROLA ASYCHRONOUS MODE INTERFACE SIGNALS DURING PROGRAMMED I/O READ AND WRITE OPERATIONS
READ OPERATION
ALE_AS t0 ADDR[6:0] t3 CS Valid Address t3 t0 Valid Address
W RITE OPERATION
DATA[7:0] t1 RD_DS
Valid Data for Readback t1
Data Available to W rite Into the LIU
W R_R/W
t2 t2
RDY_DTACK
TABLE 27: MOTOROLA ASYCHRONOUS MODE MICROPROCESSOR INTERFACE TIMING SPECIFICATIONS
SYMBOL PARAMETER MIN MAX UNITS
t0 t1 t2 NA t3
Valid Address to CS Falling Edge CS Falling Edge to DS (Pin RD_DS) Assert DS Assert to DTACK Assert DS Pulse Width (t2) CS Falling Edge to AS (Pin ALE_AS) Falling Edge
0 0 140 0
140 -
ns ns ns ns ns
136
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION POWER PC 403 SYCHRONOUS INTERFACE TIMING The signals used in the Power PC 403 Synchronus microprocessor interface mode are: Address Strobe (AS), Microprocessor Clock (uPCLK), Data Strobe (DS), Read/Write Enable (R/W), Chip Select (CS), Address and Data bits. The interface timing is shown in Figure 119. The I/O specifications are shown in Table 28.
REV. 1.2.0
FIGURE 119. POWER PC 403 INTERFACE SIGNALS DURING PROGRAMMED I/O READ AND WRITE OPERATIONS
READ OPERATION WRITE OPERATION
TS tdc uPCLK t0 ADDR[14:0] t3 CS tcp t0 Valid Address t3
Valid Address
DATA[7:0]
Valid Data for Readback t1
Data Available to Write Into the LIU
WE
R/W
t2 t2
TA
TABLE 28: POWER PC 403 MICROPROCESSOR INTERFACE TIMING SPECIFICATIONS
SYMBOL PARAMETER MIN MAX UNITS
t0 t1 t2 NA t3 tdc tcp
Valid Address to CS Falling Edge CS Falling Edge to WE Assert WE Assert to TA Assert WE Pulse Width (t2) CS Falling Edge to TS Falling Edge
PCLK Duty Cycle PCLK Clock Period
0 0 240 0 40 20
240 60 -
ns ns ns ns
% ns
137
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
ORDERING INFORMATION
PRODUCT NUMBER PACKAGE OPERATING TEMPERATURE RANGE
XRT86VL38IB XRT86VL38IB484 XRT86VL34IB XRT86VL32IB
420 Plastic Ball Grid Array 484 Shrink Thin Ball Grid Array 225 Plastic Ball Grid Array 225 Plastic Ball Grid Array
-40C to +85C -40C to +85C -40C to +85C -40C to +85C
138
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
PACKAGE DIMENSIONS FOR 420 PLASTIC BALL GRID ARRAY
REV. 1.2.0
E
420 PLASTIC Thin Ball Grid Array (35.0 mm x 35.0 mm, PBGA)
Rev. 1.00
Note: The control dimension is in millimeter. INCHES MIN MAX 0.085 0.098 0.020 0.028 0.020 0.024 0.045 0.047 1.370 1.386 1.2500 BSC 1.370 1.386 1.2500 BSC 0.024 0.035 0.0500 BSC MILLIMETERS MIN MAX 2.16 2.50 0.50 0.70 0.51 0.61 1.15 1.19 34.80 35.20 31.75 BSC 34.80 35.20 31.75 BSC 0.60 0.90 1.27 TYP.
SYMBOL A A1 A2 A3 D D1 E E1 b e
139
XRT86VL3X
REV. 1.2.0
4
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
PACKAGE DIMENSIONS FOR 484 SHRINK THIN BALL GRID ARRAY
E
484 Shrink Thin Ball Grid Array (23.0 mm x 23.0 mm, STBGA)
Rev. 1.00
Note: The control dimension is in millimeter. INCHES MIN MAX 0.071 0.082 0.019 0.022 0.019 0.022 0.033 0.037 0.898 0.913 0.8268 BSC 0.898 0.913 0.8268 BSC 0.024 0.028 0.0394 BSC MILLIMETERS MIN MAX 1.80 2.08 0.47 0.57 0.48 0.56 0.85 0.95 22.80 23.20 21.00 BSC 22.80 23.20 21.00 BSC 0.60 0.70 1.00 BSC
SYMBOL A A1 A2 A3 D D1 E E1 b e
140
XRT86VL3X
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
PACKAGE DIMENSIONS FOR 225 BALL PLASTIC BALL GRID ARRAY
REV. 1.2.0
E
225 Ball Plastic Ball Grid Array (19.0 mm x 19.0 mm, 1.0mm pitch PBGA)
Rev. 1.00
1 1 1 1 1 8 6 4 2 8 16 1 4 1 2 10 9 7 5 3 1 5 3 1 7 A B C D E F G H J K L M N P R T U V
A1 Feature / Mark
D
D1
D1 D
(A1 corner feature is mfger option)
D2 Seating Plane A A 1 b e
A 2 A 3
Note: The control dimension is in millimeter. INCHES MIN MAX 0.049 0.096 0.016 0.024 0.013 0.024 0.020 0.048 0.740 0.756 0.669 BSC 0.665 0.669 0.020 0.028 0.039 BSC MILLIMETERS MIN MAX 1.24 2.45 0.40 0.60 0.32 0.60 0.52 1.22 18.80 19.20 17.00 BSC 16.90 17.00 0.50 0.70 1.00 BSC
SYMBOL A A1 A2 A3 D D1 D2 b e
141
XRT86VL3X
REV. 1.2.0
T1/E1/J1 FRAMER/LIU COMBO - ARCHITECTURE DESCRIPTION
REVISION HISTORY
REVISION # DATE DESCRIPTION
1.2.0
7/14/06
First release of the XRT86VL3x Architecture Description.
NOTICE
EXAR Corporation reserves the right to make changes to the products contained in this publication in order to improve design, performance or reliability. EXAR Corporation assumes no responsibility for the use of any circuits described herein, conveys no license under any patent or other right, and makes no representation that the circuits are free of patent infringement. Charts and schedules contained here in are only for illustration purposes and may vary depending upon a user's specific application. While the information in this publication has been carefully checked; no responsibility, however, is assumed for inaccuracies. EXAR Corporation does not recommend the use of any of its products in life support applications where the failure or malfunction of the product can reasonably be expected to cause failure of the life support system or to significantly affect its safety or effectiveness. Products are not authorized for use in such applications unless EXAR Corporation receives, in writing, assurances to its satisfaction that: (a) the risk of injury or damage has been minimized; (b) the user assumes all such risks; (c) potential liability of EXAR Corporation is adequately protected under the circumstances. Copyright 2006 EXAR Corporation Datasheet July 2006. Reproduction, in part or whole, without the prior written consent of EXAR Corporation is prohibited.
142

▲Up To Search▲

Price & Availability of XRT86VL34IB

	To Download XRT86VL34IB Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .